Difference between revisions of "Talk:380: Emoticon"

Explain xkcd: It's 'cause you're dumb.
Jump to: navigation, search
(Trivia: new section)
(Trivia)
Line 24: Line 24:
 
== Trivia ==
 
== Trivia ==
  
==Trivia==
 
 
U+FDD0 did in fact kill at least one chat client at the time. Konversation in particular. (and presumably any other Qt-based chat clients using QTextDocument)
 
U+FDD0 did in fact kill at least one chat client at the time. Konversation in particular. (and presumably any other Qt-based chat clients using QTextDocument)
 
"basically u+fdd0 (eye of basilisk, the snake) is in a char range that's marked for interchange and illegal in utf-8"
 
"basically u+fdd0 (eye of basilisk, the snake) is in a char range that's marked for interchange and illegal in utf-8"

Revision as of 04:26, 18 November 2016

This may also be a reference or allusion to David Langford's basilisks, which are computer-generated images (mostly fractals) that kill or otherwise incapacitate people by triggering faults or overloads common to human neuropathways. ...I think it's just about the humor in a mythological basilisk's power transferring via emoticons, though. JET73L (talk) 16:05, 8 February 2013 (UTC)

<BSLSK05> :) 173.72.159.14 (talk) (please sign your comments with ~~~~)

Perhaps Cueball isn't dead, but petrified, because he saw the eyes indirectly? Like in Harry Potter. 121.99.61.70 21:10, 15 July 2013 (UTC)

The X'd eyes and skull floating above Cueball indicates that the basilisk was, indeed, successful in its task. For those concerned about the paradox between "Cueball"'s untimely demise in this comic and his future appearances, consider this a parallel reality. Your brain is safe! Thokling (talk) 05:50, 22 September 2013 (UTC)
Maybe a Poincaré recurrence time passes between this comic and the next one. 108.162.219.5 (talk) (please sign your comments with ~~~~)
...or just consider that 'Cueball' is simply the name of the 'species' of stick figure here. Otherwise, the Cueball here would still be missing a hand, literally. Greyson (talk) 03:16, 16 December 2013 (UTC)
Of course, there's no way we can tell it's not a prosthesis. --Alex (talk) 19:51, 17 May 2014 (UTC)

Is this the last comic with a CRT monitor? 89.243.117.162 20:57, 14 August 2013 (UTC)

Good question, I did add a category for this so we can collect them.--Dgbrt (talk) 20:26, 21 August 2013 (UTC)
The CTR category was deleted by Davidy so the puzzle is left unsolved Kynde (talk) 12:10, 16 May 2014 (UTC)

It would be extraordinarily like xkcd to include a reference to [Roko's Basilisk] and make it literal, in a manner similar to how other debates and ideas in computer science, mathematics, and other fields became actual battles. Consider [Pumpkin Carving] or [Principle of Explosion], where ideas from set theory and logic manifest directly in the world. Warning: some folk find the thought experiment of Roko's Basilisk disturbing. 108.162.238.166 (talk) (please sign your comments with ~~~~)

As noted above, the reference is more likely to Langford's basilisks (though the rest of your comment fits just as well). Though now I at least have an idea why is Roko's Basilisk named that... I kept wondering "why is this thought experiment in any way similar to a basilisk?" --141.101.81.74 06:37, 9 November 2015 (UTC)
For that matter, this particular comic is early enough that it actually predates the Roko's Basilisk story. --141.101.81.78 15:24, 10 November 2015 (UTC)
What's up with the explanation??

The explanation is super messy, can someone who understands it fix it? 162.158.133.120 (talk) (please sign your comments with ~~~~)

Trivia

U+FDD0 did in fact kill at least one chat client at the time. Konversation in particular. (and presumably any other Qt-based chat clients using QTextDocument) "basically u+fdd0 (eye of basilisk, the snake) is in a char range that's marked for interchange and illegal in utf-8" "but qt's utf-8 encoder let it through anyway" "but it just so happens that qt's qtextdocument uses u+fdd0 as text frame delimiter" "so when you append it to a qtd, counters run wrong and eventually you crash" "d-bus closes the connection and crashes the client when it encounters illegal utf-8, and kde's notification system works through d-bus" The problem was fixed after the xkcd "report" and Konversation now handles unicode normally.