1700: New Bug - Revision history

FaviFake at 13:17, 29 July 2025

2025-07-29T13:17:53Z

Maplestrip: /* Explanation */ Simplifying.

2024-04-08T07:37:13Z

‎Explanation: Simplifying.

Misterblu28: happy 1000 comic anniversary

2022-11-19T17:08:57Z

happy 1000 comic anniversary

Jacky720: rv

2022-05-04T21:10:14Z

Show changes

Ex Kay Cee Dee at 21:10, 4 May 2022

2022-05-04T21:10:12Z

Show changes

Jacky720: rv

2022-05-04T20:56:07Z

Show changes

Ex Kay Cee Dee at 20:47, 4 May 2022

2022-05-04T20:47:35Z

Show changes

Davidy22: Reverted edits by X. K. C. D. (talk) to last revision by 172.70.131.214

2022-05-04T01:59:31Z

Reverted edits by X. K. C. D. (talk) to last revision by 172.70.131.214

Show changes

X. K. C. D. at 00:53, 4 May 2022

2022-05-04T00:53:51Z

Show changes

172.70.131.214: /* Explanation */

2022-03-30T13:25:24Z

‎Explanation

@@ Line 48: / Line 48: @@
 [[Category:Emoji]]
 [[Category:Unicode]]
-[[Category:Cueball Computer Problems]]
+[[Category:Cueball's computer problems]]

@@ Line 18: / Line 18: @@
 The title text shows that his general approach to problems is not to actually fix bugs but to work around them and even rely on them for other behavior. This approach to software development makes for terrible code, which is likely how Cueball got into this trouble in the first place. Therefore the title text shows that he still has yet to learn from his mistakes, further supporting the suggestion to just burn the whole thing down.
-In the title text of the first, using emoji in variable names is mentioned. Emoji has since then become a [[:Category:Emoji|recurrent theme]] on xkcd.
+Emoji are a [[:Category:Emoji|recurrent theme]] on xkcd.
 In [[1349: Shouldn't Be Hard]], Cueball is also programming and finding it very difficult, although he thinks it should be easy. An off-panel person suggests burning the computer down with a blowtorch, much like the off-panel person in this one suggests burning the whole project (including the computer) to the ground with lighter fluid. In the next comic, with multiple storylines [[1350: Lorenz]], one [http://xkcd.com/1350/#p:2ed958de-badf-11e3-8001-002590d77bdd story line] results in a computer being [http://www.explainxkcd.com/wiki/images/a/a6/lorenz_-_laptop_9.png burned with a blow torch].

← Older revision		Revision as of 17:08, 19 November 2022
Line 21:		Line 21:

	In [[1349: Shouldn't Be Hard]], Cueball is also programming and finding it very difficult, although he thinks it should be easy. An off-panel person suggests burning the computer down with a blowtorch, much like the off-panel person in this one suggests burning the whole project (including the computer) to the ground with lighter fluid. In the next comic, with multiple storylines [[1350: Lorenz]], one [http://xkcd.com/1350/#p:2ed958de-badf-11e3-8001-002590d77bdd story line] results in a computer being [http://www.explainxkcd.com/wiki/images/a/a6/lorenz_-_laptop_9.png burned with a blow torch].		In [[1349: Shouldn't Be Hard]], Cueball is also programming and finding it very difficult, although he thinks it should be easy. An off-panel person suggests burning the computer down with a blowtorch, much like the off-panel person in this one suggests burning the whole project (including the computer) to the ground with lighter fluid. In the next comic, with multiple storylines [[1350: Lorenz]], one [http://xkcd.com/1350/#p:2ed958de-badf-11e3-8001-002590d77bdd story line] results in a computer being [http://www.explainxkcd.com/wiki/images/a/a6/lorenz_-_laptop_9.png burned with a blow torch].
		+
		+	Exactly [[2700: Account Problems\|one thousand comics later]], Cueball is still running into technical problems with abnormal passwords.

	Interestingly, the 2021 vulnerability {{w\|Log4Shell\|Log4Shell}} could be triggered when a specially crafted URL was logged with the Log4j framework. This could lead to a crash (as in the comic) or the computer being taken over by the attacker. However, the contents of a password field should never be logged, so this still would indicate a major problem with the design of Cueball's project.		Interestingly, the 2021 vulnerability {{w\|Log4Shell\|Log4Shell}} could be triggered when a specially crafted URL was logged with the Log4j framework. This could lead to a crash (as in the comic) or the computer being taken over by the attacker. However, the contents of a password field should never be logged, so this still would indicate a major problem with the design of Cueball's project.

@@ Line 10: / Line 10: @@
 [[Cueball]] asks if an off-panel character can look at his bug report. The person asks if it's a "normal one," and not a "horrifying" one which proves that the entire project is "broken beyond repair and should be burned to the ground." This implies that there have been reports of the "horrifying" variety in the past.
-Cueball promises that it is a normal one but it turns out that the server crashes when a user's password is a resolvable URL, which implies that the server is in some way attempting to resolve passwords as if they were URLs. A resolvable URL is one that is syntactically correct and refers to a find-able and accessible resource on the internet (i.e. does not return a {{w|HTTP_404|404 error}} or equivalent when resolved). Therefore a resolvable URL is a {{w|fully qualified domain name}} or a valid IP address that points to a valid server, and it can optionally specify a resource that exists on that server. Normally there is no reason for a system to treat a password as if it were a URL — and testing if a password is a resolvable URL would be a horrible thing to do as it would involve sending the password over the internet in a (at the time the comic was written) most likely completely unencrypted version.
+Cueball promises that it is a normal one but it turns out that the server crashes when a user's password is a resolvable URL, which implies that the server is in some way attempting to resolve passwords as if they were URLs. A resolvable URL is one that is syntactically correct and refers to a find-able and accessible resource on the internet (i.e. does not return a {{w|HTTP_404|404 error}} or equivalent when resolved). Therefore a resolvable URL is a {{w|fully qualified domain name}} or a valid IP address that points to a valid server, and it can optionally specify a resource that exists on that server. Normally there is no reason for a system to treat a password as if it were a URL — and testing if a password is a resolvable URL would be a horrible thing to do as it would involve sending the password over the internet in a (at the time the comic was written) most likely completely unencrypted format.
 Also, Cueball specifically states that the server is crashing, rather than his application. While this could be an example of misused terminology on the part of Cueball or Randall, given Cueball's history (for example causing the most basic console commands to fail in [[1084: Server Problem]] or other tech issues as seen in [[1586: Keyboard Problems]]) his choice of terms is probably accurate. In the context of web services the server refers to either the computer itself or the program that responds to web requests and executes the user's (i.e. Cueball's) application. Cueball would be in charge of building the application. The importance of this distinction is that a typical system has safe guards in place at many levels to prevent a misbehaving application from crashing anything other than itself. So for his application to crash the server (either the computer itself or the server software hosting his application) would require his application to be operating in a way far outside of the normal, which has been the case for Cueball in previous comics. Alternatively, the project might include its own server software without the safeguards. In either case it is clear that Cueball's issue is far from normal, for which reason the off-panel person gives up and decides that burning the project to the ground is the only solution, telling Cueball ''I'll get the {{w|Charcoal_lighter_fluid|lighter fluid}}''.