explain xkcd - User contributions [en]

2916: Machine

2024-04-15T08:07:43Z

141.101.98.114: /* Explanation */

{{comic
| number = 2916
| date = April 5, 2024
| title = Machine
| image = machine_2x.png
| imagesize = 740x740px
| noexpand = true
| titletext = The Credible Machine
}}
* To experience the interactivity, visit the [https://xkcd.com/2916/ original comic].

==Explanation==
{{incomplete|Created by a WELL OILED ROBOT. Do NOT delete this tag too soon.}}
This interactive game is the 14th [[:Category:April fools' comics|April fools' comic]] released by [[Randall]]. The previous April fools' comic was [[2765: Escape Speed]] from 2023, which was released on Wednesday, April 19, 2023.

As referenced in the title text, this game is a spiritual successor to the 1990s and early 2000s PC puzzle game series {{w|The Incredible Machine}}, a game Randall played as a kid. Both games have several objects in common:
* fan
* cat
* ramps
* balls of various density

The comic starts in a main screen where the user can create a {{w|Rube Goldberg machine}} in a "Cell" where the goal is to route a constant stream of colored balls from inputs on the ceiling or walls to outputs of matching colors on the walls or floor. After the comic is first opened a window pops up over the machine where Cueball in a lab coat tells you to route the balls from the inputs to the outputs. A button opens a “tool panel” where there are large and small boards available for use, as well as some gimmicky stuff like prisms (which deflect marbles) and fans (which blow marbles around), and decorative elements which have no effect on the balls.

Typically, inputs and outputs only accept balls of a single color. However, some outputs accept multiple colors, indicated by a double arrow, and some inputs produce multiple colors. When the player is designing their 'machine', this will involve multiple full streams merged into one (supplied by a double-exit on the adjacent submission). Machines now working in the full grid may, however, find that their sources now contain stray balls of other types that were not handled properly, but there is no way to force a re-edit of the machine to alter its behavior to account for this.

If any balls are left in your cell for more than 30 seconds, they fade away. The first time a ball fades away another popup informs you that the balls are removed for security reasons. A counter increases for each ball of the correct color that passes through an exit, and reduces when no balls pass through, or if balls of the wrong color pass through it. An indicator next to each exit shows whether that exit is not properly supplied (with a cross) or is receiving above its required threshold (a tick). The first time you have built a machine which succeeds in routing enough balls of the correct color to ''all'' relevent outputs, a popup will prompt you to submit your cell to be added to the public machine. (Subsequently, the submit button will quietly change from 'inactive' (pale) to clickable (dark). This will change back again if any ball transfers again dip back below the required threshold for any reason, such as further editing or an end to a 'fluke' glut of accumulated balls.)

Choosing to submit your cell will give you a textbox to give this cell a name. Proceeding through that, you will now see your cell within the 'grid' and a 'live' feed of balls from any relevent neighboring cells (which may be more sporadic then the feed you designed your cell with, and contain stray balls of different types). If any supplying-neighbors are still marked as "under construction", they ''may'' provide the balls as if perfectly routed from their own (eventual) source, but will eventually dry up.

It is unknown exactly how and why a particular submission becomes a permanent part of the grid, but your solution may not remain the one used in future refreshes of the grid (e.g. after you choose to edit another randomly allocated cell-in-waiting). The cell you have worked on may even be seen to be an "Under construction" cell in future grid-views and/or given back to you as an (empty) editable area when you choose to change back to the construction-mode. Given the number of 'bottom-layer' cells that are likely primed ready to be completed (e.g. the grid-width of twelve, perhaps staggered across adjacent rows) and the many possible worldwide contributors at any one time, it may be that the chances of being picked for permanence is low; and certainly would have been early on in the comic's existence during the initial frantic rush to participate.

<gallery heights="200" widths="150">
File:2916_popup_intro.png|Introduction popup
File:2916_popup_time.png|Time limit popup
File:2916_popup_submit.png|Submission popup
</gallery>

The button in the bottom right corner allows you to toggle between editing your own machine and a page where you can drag around to view all of the machines that have been submitted and accepted, with a title for each in the upper left corner. In this view you can see that all of the outputs are also inputs for another cell, except for the top row where the inputs come from off screen and the lowest row which output through a launcher of some kind to a set of four colored-coded containers far below. Any empty cells are marked off by yellow tape with the words "UNDER CONSTRUCTION" as well as "DJIA ↑ 31415" once in each cell. "DJIA" stands for the Dow Jones Industrial Average, with "DJIA ↑ 31415" indicating that it rose to 31415 points, 31415 being the first five digits of pi, without the period. This would often be displayed on a yellow 'ticker', which might look superficially similar to the yellow barrier tape.

When viewing the whole machine, a button in the bottom left corner, added later, allows you to follow the path of the nearest ball as it passes from cell to cell. This will also make the ball you are following immortal - not subject to the 30s timeout rule. Another later addition was a button in the top left corner which copies a URL that will take you directly to the current cell that you are viewing. However, the link that is created will always show you the version of the machine at the time that you were viewing it, without any subsequent additions.

Whenever balls reach the bottom of the grid, they are directed towards four containers, one of each color. Most balls are accurately sent to their appropriate container, though there are some misfires. These containers are above a pit, and periodically dump their contents. Balls in the pit are subject to the same 30s culling rule as balls in the cells above. If no balls are directed towards the containers, the pit will be empty. If one or two streams of balls are making it, Cueball and Megan sit in a small boat named the USS Buoyancy, and when sufficient balls are being deposited, the boat begins to float and move. More streams of balls are likely to add more changes. Balls which miss or overspill the pit fall out of the bottom of the frame.

Under construction cells will feed balls of the appropriate color into neighboring cells so long as you are not looking at them. Once you scroll to look at them, the supply of balls stops and subsequent cells in the chain will not receive any; scroll away from them again and the supply will resume.

When you press submit, you will see your creation placed on the grid. However if you refresh that cell will likely be under construction or replaced with someone else's machine. However, other people's machines are consistently placed, so it appears that there is some moderation process selecting a machine for each cell out of the machines submitted by users. If your newly submitted creation is placed in the lowest row of cells, balls will be dispensed through the exit at the bottom, but there will be no launcher to propel them towards the pit, and they will vanish as they leave the exit.

The grid is 12 cells wide, and grows in height. The largest size observed so far is 12x65, for a total of 780 cells. The machine's height is determined by the lowest cell; This can be either your submitted cell, or a cell created by another user.

Imperfections in the machines (whether accidental or by design) and the impossibility of entirely avoiding collisions when crossing streams inevitably lead to significant levels of losses and pollution with the wrong color balls. Indeed, using the follow ball trick (see Trivia) appears to show that it is quite rare for a ball to survive more than several machines without getting stuck somewhere. This implies that there is some 'creative accounting' going on to ensure that cells lower in the grid still have balls to process - simulating flow only for a few nearby cells, while assuming that those cells themselves have pure, steady inputs.

There is a hard limit of 100 items (both physically interactive and purely decorative) that can be placed in any given arena. If you have placed 75 items, a count will appear in the component bar of your piece-count ("''##''/100"), which will go away again if you delete items to below the limit. The count text turns red at "100/100", at which point no more items can be added, only existing ones moved (or removed, to lower the count again).

===Toolbox items===
{| class="wikitable" style="margin:auto"
|+ List of objects
|-
! Description !! Effect !! Image
|-
| Plank || Static obstacle || [[File:2916_plank.png|frameless|upright=0.25]]
|-
| Hammer || Static obstacle || [[File:2916_hammer.png|frameless|upright=0.25]]
|-
| Sword || Static obstacle || [[File:2916_sword.png|frameless|upright=0.25]]
|-
| Hinged scoop&dagger; || Rotates around its hinge, tries to stay horizontal with a springy effect || [[File:2916_scoop.png|frameless|upright=0.25]] [[File:2916_scoop_mirrored.png|frameless|upright=0.25]]
|-
| Anvil || Static obstacle || [[File:2916_anvil.png|frameless|upright=0.125]]
|-
| Brick || Static obstacle || [[File:2916_brick.png|frameless|upright=0.125]]
|-
| Fan || Blows away balls in front of it. Different colors are affected by differing amounts (yellow balls are lightest, and can be levitated above an upward-facing fan).|| [[File:2916_fan.png|frameless|upright=0.125]]
|-
| Pillow || Balls will not bounce if they hit it || [[File:2916_pillow.png|frameless|upright=0.125]]
|-
| Bumper || Bounces balls away at significantly higher speed || [[File:2916_round_bumper.png|frameless|upright=0.125]] [[File:2916_bumper_left.png|frameless|upright=0.125]] [[File:2916_bumper_right.png|frameless|upright=0.125]]
|-
| Attractor/Black Hole* || Pulls balls toward center || [[File:2916_attractor.png|frameless|upright=0.125]]
|-
| Repulsor/White hole* || Repels balls away from center || [[File:2916_repulsor.png|frameless|upright=0.125]]
|-
| Prism || "Refracts" and internally-reflects balls as they otherwise pass through the object, the color of the ball ''may'' cause them to react (as much as possible) according to the respective color across the element. || [[File:2916_prism.png|frameless|upright=0.125]]
|-
| Wheel&Dagger; || Spins, deflects balls, can jam with enough resistance (e.g. glut of balls or against other elements). || [[File:2916_wheel.png|frameless|upright=0.125]]
|-
| "Good job" trophy || Static obstacle || [[File:2916_trophy.png|frameless|upright=0.125]]
|-
| Glass cup || Static obstacle. Container, with a nominal capacity of up to four balls (in whole or in part) within it. || [[File:2916_cup.png|frameless|upright=0.125]]
|-
| Cat || Swats away balls in front of itself (was added later) || [[File:2916_cat_new.png|frameless|upright=0.25]]
|-
! colspan="3" style="text-align:center" | Non-physical items
|-
| Right-facing Ponytail, with raised arms || Intangible decoration || [[File:2916_ponytail_arms.png|frameless|upright=0.125]]
|-
| Right-facing Ponytail, standing || Intangible decoration || [[File:2916_ponytail.png|frameless|upright=0.125]]
|-
| Left-facing Cueball, with raised arms || Intangible decoration || [[File:2916_cueball_arms.png|frameless|upright=0.125]]
|-
| Left-facing White Hat, standing || Intangible decoration || [[File:2916_whitehat.png|frameless|upright=0.125]]
|-
| Rightwards-facing Knit Cap, in an 'action' pose || Intangible decoration || [[File:2916_knitcap_resting.png|frameless|upright=0.25]]
|-
| Right-facing Knit Cap, standing || Intangible decoration || [[File:2916_knitcap.png|frameless|upright=0.125]]
|-
| Helmet-wearing figure, standing || Intangible decoration || [[File:2916_helmet.png|frameless|upright=0.125]]
|-
| Squirrel || Intangible decoration || [[File:2916_squirrel.png|frameless|upright=0.125]]
|-
| "Probably Deterministic" sign || Intangible decoration || [[File:2916_deterministic.png|frameless|upright=0.25]]
|-
| [[1682: Bun|Bun]] || Intangible decoration || [[File:2916_rabbit.png|frameless|upright=0.125]]
|-
| Cat || Intangible decoration || [[File:2916_cat.png|frameless|upright=0.125]]
|}

:<nowiki/>* — The Attractor and Repulsor are omnidirectional, but the area of effect can be resized to extend or restrict its influence. You do this by way of its bounding box with corner and mid-edged 'drag nodes' and a circular area that shows the current extent, which are only visible when the element is actively selected. This resize can be no larger than will make the box/circle touch the edges, no smaller than the fixed graphic and will always be identically proportioned in both axes.

:&dagger; — The hinged scoops are strictly horizontal, on building. They will rotate away from and (spring back to) horizontal according to interactions with balls or other non-decorative items that may be placed to disturb their balance, sometimes with further interesting interactions (that may or may not be intentional or useful). There are two selectable versions of this item. (The only ''other'' object class with a clear (and practical) asymmetry, for which a mirrored chirality can be chosen from the sidebar, are the two versions of triangular "Bonk"-bumpers.)

:&Dagger; — The wheel is an actively rotating element that starts off, by default, spinning anticlockwise. Pressing or tapping left/right arrow keys, when a placed wheel is selected, will adjust that wheel's rotation rate to be more/less anticlockwise. Adjusting it beyond zero rotation allows you to make it spin in the opposite direction.
:Rotation can be increased well beyond the point at which the {{w|wagon-wheel effect}} occurs, which may make it difficult to work out the spin direction of an overspeed wheel element (and thus which arrow keys will slow or speed up its rotation, if you have forgotten), though observing its impact upon any balls that strike it ''should'' make its current spin-direction obvious.
:The 'bounding editing box' will usually appear rotated, possibly according to the spinning graphic's current orientation upon selection, but remains at that (often non-orthagonal) angle even as the wheel spins (if it can) during this period of selection for editing.

All other items can be manually re-angled by a 'loop node' arm extending from the bounding box. If you cannot see the 'angle node' for such a selected item, which is normally at the top of any freshly placed item but follows any re-angling that may have already applied, it could be that you have placed the item too close to the edge in which direction the node extends. To rotate it, move the object away from the edge to access the construction node (after which, you can drag the object back if required – but see below).

Rotation may be limited by the {{w|minimum bounding box}} that is the 'selection box', this is not necessarily the more flush {{w|convex hull}} of the collision-map built into the graphic. Should a corner of the bounding box need to move across the edge of the build-area, it will do nothing more than touch the edge until there is sufficient angle-drag to snap it to the angle from which that corner now comes back away from the edge; or, when it has a long straight edge currently flush with the edge boundary, it may snap to exactly 180°, in rotation, whereupon the opposite long straight edge is flush to the construction area edge. All objects that are drag-moved, similarly, cannot be moved any further than their current bounding box touching the construction-area edging. The bounding box for the rotating wheel is a notable exception to this, being not under any direct angle-control by the player. Instead, it seems to use the bounding inscribed circle that defines the wheel edge iteslf.

Apart from some interactions between the hinged scoops and any element (including other hinged scoops), there is no preventative 'collision detection' between objects during user-placement, which may overlap/cover each other (the most recently spawned item graphically overlays any earlier one). The wheel object will only spin if not constrained by other physical elements (including the spokes of an adjacent wheel, not in counter-rotation) but can still be dragged and placed anywhere within the boundary of the construction area.

The continuous stream(s) of balls respect all ''tangible'' objects, which includes any currently being dragged/rotated, though may prematurely vanish if forced between two items moved to touch/overlap each other. It is possible to to indirectly nudge balls by carefully moving a tangible object's surface into them (or holding them within it, e.g. the "cup"). This may be useful for rescuing temporarily stray balls (before they time-out anyway), unjamming an area with a construction-induced glut ''or'' for testing a ball-path that is not currently being fed 'naturally'. Doing so ''can'' then conceivably fulfil all the exit-gate requirements (temporarily), as it might also transiently spoil some required routing, but the manual intervention will not be possible once a 'machine' has been submit.

===Non-player items===

Ball containers at the bottom of the machine
{|
|[[File:2916_container_red.png|thumb|center|50px]]
|[[File:2916_container_yellow.png|thumb|center|50px]]
|[[File:2916_container_blue.png|thumb|center|50px]]
|[[File:2916_container_green.png|thumb|center|50px]]
|}

Cueball and Megan in the ''USS Buoyancy''
[[File:4d425c.png|thumb|left|150px]]
 

Pit below the ''USS Buoyancy'' (not to scale)
[[File:2916_pit_bottom.png|thumb|left|300px]]
 

=== Color routing ===
The different ball colors have different physical properties. Red balls are more bouncy than other balls, green balls are heavier, and yellow balls are lighter and slightly bouncy. The following values were extracted from the code:
{| class="wikitable sortable"
! Color
! Mass
! Density
! Restitution (bounciness)
! Linear damping (drag)
|-
! data-sort-key="00F" | Blue
| 0.08
| 1
| 0
| 0
|-
! data-sort-key="F00" | Red
| 0.08
| 1
| 0.8
| 0
|-
! data-sort-key="0F0" | Green
| 0.75
| 9.325
| 0
| 0
|-
! data-sort-key="FF0" | Yellow
| 0.024
| 0.3
| 0.6
| 2
|}

For certain combinations of inlet and outlet 'gates', it is necessary to 'cross the streams'. e.g. to direct righthand-entry balls to a lefthand-exit and vice-versa. It is possible to just construct the field to send two (or more!) sets of balls to fly across a common gap, to land on an appropriate reception area that leads to the chosen exit. But, though this is not {{w|Proton pack#Crossing the streams|completely inadvised}}, the timing of the balls cannot be guaranteed to be in sync (or, rather, anti-sync) with each other and collisions ''will'' occur, especially under the variations of delivery that might significantly alter the ballistic path across the gap. Even if the trial machine works, in isolation with a steady stream of all balls entering the field of play, once submitted it will inevitably be fed by a more chaotically-routed preceeding construction.

In order to maintain sufficient correct arrivals at exits, it may be necessary to add a method of filtering the hues.

This could just mean introducing a 'wrong hue trap' beyond any crossing point(s) that send the occasionally wrong ball back to the cross point (or let them time-out in a dead-end, relying upon few enough failures from the rest of the balls, along with all colliding balls that subsequently missed ''any'' chance of reaching an exit). Alternatively, two (or more) feeds of marbles could be fed through a deliberate 'sorter' that does a sufficiently reasonable job of separating the combined sets out towards their intended target-exits.

The various physical qualities of the balls suggest a number of methods for redirecting separate hues to separate onward journeys. This can be done by isolating a hue from every other hue, then passing on (if necessary) to a setup extracting a different one from the remainder, and perhaps also a third time. It may also be possible to merge 'arrangements' of sorting mechanics to efficiently distribute straight into three ''or even four'' onward tracks towards the desired outputs, but that is left as an exercise to the reader.


{| class="wikitable"
! style="background-color:black; color:white" | To separate !! style="background-color:lightblue" | Blue !! style="background-color:lightgreen" | Green !! style="background-color:yellow" | Yellow !! style="background-color:red" | Red
|-
! style="background-color:red" | Red
| *R/B* | '''Use 'bounce''''
The sole difference is how much balls will rebound from objects. Well managed and constrained ricochets should allow a sorting action.
| *R/G* | '''Use mass or 'bounce''''
Green balls cannot be levitated by a vertical fan. An incline across any such fan(s) will levitate only non-Greens. Green, like Blue, rebounds differently to Red. Green balls are also affected by black holes much less than all other balls.
| *R/Y* | ''See Y/B''
| *R/R* style="text-align: center; background-color:black; color:white" | n/a
|-
! style="background-color:yellow" | Yellow
| *Y/B* | '''All methods'''
Yellow, alone, exhibits high drag against any unforced motion. It is also unique in all other ways; e.g. can be levitated highest, against all other hues (though most profoundly against Green).
| *Y/G* | ''See Y/B''
| *Y/Y* style="text-align: center; background-color:black; color:white" | n/a
| *Y/R* style="text-align: center; background-color:gray" | ''See Y/B'' 
|-
! style="background-color:lightgreen" | Green
| *G/B* | '''Use mass'''
Green balls cannot be levitated by a vertical fan. There is also a not so marginal difference in density that might be exploited, such as by using black holes, which only minimally effects Green (perhaps showing an effective difference between mass of attraction and mass of inertia).
| *G/G* style="text-align: center; background-color:black; color:white" | n/a
| *G/Y* style="text-align: center; background-color:gray" | ''See Y/B'' 
| *G/R* style="text-align: center; background-color:gray" | See R/G
|-
! style="background-color:lightblue" | Blue
| *B/B* style="text-align: center; background-color:black; color:white" | n/a
| *B/G* style="text-align: center; background-color:gray" | See G/B
| *B/Y* style="text-align: center; background-color:gray" | See Y/B
| *B/R* style="text-align: center; background-color:gray" | See R/B
|}

Even when not strictly necessary for one's own submission, once submitted into the full playing grid the player's own contribution may find itself working with less 'pure' delivered ball-streams (from an imperfectly separating feed-in contribution). It is possible that this more interactive disruption can make the new setup behave erratically or even entirely incorrectly.

It might be thought good practice (but not ''necessary'') to deliberately combine any or all inputs and do a full job of splitting them again, just in anticipation of possibly having to deal with such cross-contamination and being able to 'clean up' the onward stream(s) for the benefit of others. This would of course be particularly difficult if the isolated building-phase does not provide all four hues to 'test' against, so any speculatively added filtering would have to be added 'blind' (and only on the offchance that any anticipated incorrect balls will actually enter the arena) and without any legitimate exits to which such rejects could be shunted (therefore could accumulate, up until any 'time out' that might apply to any ball once operational as part of the combined grid).

Single-input/single-output designs might not particularly require ''any'' sorting mechanism, in theory, though the unexpected 'contamination' of the system with balls of different masses/etc could perhaps introduce malfunctioning passage from the added chaos it might succumb to.

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

:[The placeholder image shows four balls, colored red, green, yellow and blue, bouncing on top of three white blocks. Text in the center: "[visit xkcd.com to view]"]

:[Cueball with lab coat, intro popup]
:Cueball: Balls falling into your cell should be routed to the outputs at a steady rate.

:[Cueball with lab coat, warning popup]
:Cueball: For security reasons, balls that remain in your device for more than 30 seconds will be removed and destroyed.

:[Cueball with lab coat, submit popup]
:Cueball: Congratulations! Your contraption has passed all tests. Press [submit button] to submit it to be added to the machine!

==Trivia==
Once again an April Fool's Day Comic came out late, as Randall did not release this on April 1st, even though April 1st did fall on a Monday, a normal release day. It first came four days later with the Friday release on April 5th. That this is to be considered an April fools' comic, in spite of the later release, was confirmed on the xkcd Facebook page.

*Randall acknowledges the people who helped him create this comic in a [[Header_text#Machine|comic-specific header text]].
**With 11 different involved apart from Randall this is by far the comic with most people involved.
*Some hidden keyboard shortcuts have been found:
** Follow balls: Ctrl + Alt/Option + B (now also accessible by using the button provided)
** Show debug overlay: Ctrl + Shift + Win/Cmd + D
*** This may particularly clash with browser functionality, e.g. Firefox's "New Bookmarks" dialogue which will need closing, though still activating the overlay graphics.
** Delete selected item: Delete (Fn + Delete on Mac)
*When Randall posted a [https://www.facebook.com/TheXKCD/posts/pfbid0Cs97awQZi1ZiaEXouAex9tXrwAS3qJV3RmAiuCq5uvZQwqZVMgDmcqJ7JU9LYodYl link to this comic] on his [https://www.facebook.com/TheXKCD Facebook feed], he directly wrote that it was a late April Fools' Day!
**MACHINE
**Happy Belated April Fool's Day!
**This thus ends any discussion of whether this should be seen as an April Fool's comic or not.
**It just came out 4 days late. This has also happened several times since [[Garden]].
[[File:2916 Machine Facebook April fools' confirmation.png]]

{{comic discussion}}

[[Category:April fools' comics]]
[[Category:Comics with color]]
[[Category:Dynamic comics]]
[[Category:Comics with animation]]
[[Category:Interactive comics]]
[[Category:Comics featuring Cueball]]
[[Category:Comics featuring Megan]]
[[Category:Comics featuring Ponytail]]
[[Category:Comics featuring White Hat]]
[[Category:Comics featuring Knit Cap]]
[[Category:Characters with hats]]
[[Category:Squirrels]]
[[Category:Buns]]
[[Category:Cats]]

1726: Unicode

2016-08-30T07:12:45Z

141.101.98.114: /* Explanation */ added dinosaur-denial

{{comic
| number = 1726
| date = August 29, 2016
| title = Unicode
| image = unicode.png
| titletext = I'm excited about the proposal to add a "brontosaurus" emoji codepoint because it has the potential to bring together a half-dozen different groups of pedantic people into a single glorious internet argument.
}}

==Explanation==
{{incomplete|first time making page. Needs much more work including links, sources and the Brontosaurus reference.}}

Cueball, along with two other figures, is placing traffic signs in a river. As rivers flow according to the landscape, this plan will not work and the river will continue on its course. Cueball is very frustrated by this and is still trying to make the river obey traffic laws. The caption lays out the punchline: the comic compares the useless approach of Cueball attempting to divert a flowing, moving river with fixed signs that do nothing, with the {{w|Unicode Consortium}}'s attempt to define the diverse and ever-changing human language with strict technical standards.

{{w|Unicode}} is a largely successful attempt to have a standard for representing all possible letters, numerals, digits and symbols that make up human writing in all languages. This includes the roman letters used in this article, characters with modifiers like ê (both with the common characters as well as the modifiers selectable separately), ideographic characters like in Chinese, syllabic writing system like Japanese, right-to-left and/or top-to-bottom writing systems, mathematical symbols, emoji, and many other writing systems. The symbols on the signs in the river, are, in fact Unicode, with the warning sign triangle with an exclamation mark ⚠ having code (U+26A0) and the black, rightwards arrow ➡ having code (U+271A). As can be imagined, coping with the wide variety of character sizes, orientations, ways they can be modified, capitalization rules, etc. can get to be very challenging as the Unicode Consortium tries to write rules that accommodate how printed language is actually used.

The title text refers to a proposal to add three dinosaur heads to the official list of emoji. This is likely to stir debate between the following opposing camps:
*those who favor the inclusion of more emoji vs. those who oppose emoji on principle
*those who accept the existence of ''Brontosaurus'' vs. those who deny its status as a species unique from ''Apatosaurus''
*those who favor a traditional, scaly image of dinosaurs vs. those who have accepted the feathered-dinosaur paradigm
*those who point out that two of the dinosaurs in the "Jurassic Emoji" set actually come from the Cretaceous period, and as such renaming is necessary vs. those who think that "Jurassic" is a cooler word
*those who for religious or other reasons deny the existence of dinosaurs.

===See also===
[[636: Brontosaurus]]

* [http://unicode.org/L2/L2016/16072-jurassic-emoji.pdf Jurassic Emoji proposal]; [http://www.unicode.org/L2/L2016/16103-jurassic-fdbk.pdf initial feedback]; [http://www.courtneymilan.com/dino/ Proposer's timeline/status page]
* [http://www.fileformat.info/info/unicode/char/26a0/index.htm Unicode Character 'WARNING SIGN']
* [http://www.fileformat.info/info/unicode/char/27a1/index.htm Unicode Character 'BLACK RIGHTWARDS ARROW']

==Transcript==
[Single panel scene: [[Cueball]] is standing waist-deep in a river. With one arm he is holding on to a traffic sign that says "Detour" with an arrow pointing to the right. The other arm is pointing horizontally. Further up the river is another street sign apparently in around 0.5 metres of water; this sign has an exclamation mark inside a triangle. In the distance on one bank of the river, two people are standing and making gestures, with a sign lying on the ground next to them. Behind them is a parked car on a road that crosses a bridge over the river.]

Cueball: No, go ''this'' way, not —

Are you even ''listening''!?

… ''Hey! That's not what this area is for!''

[Caption]

Watching the Unicode people try to govern the infinite chaos of human language with consistent technical standards is like watching highway engineers try to steer a river using traffic signs.

{{comic discussion}}

[[Category:Comics featuring Cueball]]

Talk:1725: Linear Regression

2016-08-27T16:39:32Z

141.101.98.114:

It also seems likely that the teapot refers to the Utah Teapot (https://en.wikipedia.org/wiki/Utah_teapot). It was one of the first complex 3D objects defined for CGI rendering, and has seen countless uses since. Notably in the Pipes screensaver, and early SIGGRAPH papers where it was rendered along side the 5 platonic solids as if it belonged with them.
[[User:Dkfenger|Dkfenger]] ([[User talk:Dkfenger|talk]]) 17:10, 26 August 2016 (UTC)
: I'm not sure I follow. How do you reach that conclusion? Given that the concept of constellations (and thus stars) is clearly shown in the comic, it seems much more likely to me that he was referring to Russell's Teapot and not to a computer rendering (if there was any reference at all). The fact that that shape could abstractly resemble a teapot may be all that there is to it. :) [[User:KieferSkunk|KieferSkunk]] ([[User talk:KieferSkunk|talk]]) 18:06, 26 August 2016 (UTC)

I think that the teapot is a reference to the constellation Sagittarius. This seems most likely to me as the reference is to a constellation that looks like a teapot despite ostensibly being something else. Sagittarius is a constellation that is supposed to be an archer, but many people see it as a teapot instead. (http://www.space.com/30274-constellation-sagittarius-archer-dipper-teapot.html) [[User:Harperska|Harperska]] ([[User talk:Harperska|talk]]) 19:27, 26 August 2016 (UTC)

I think it looks like a alcohol drink with the little umbrella sticking out. [[User:Mikemk|Mikemk]] ([[User talk:Mikemk|talk]]) 06:25, 27 August 2016 (UTC)

Based on what is an R^2 value of 0.06 significant??? I'm removing that. [[User:Djbrasier|Djbrasier]] ([[User talk:Djbrasier|talk]]) 20:59, 26 August 2016 (UTC)
: Oops, misread it! I read "insignificant" as "significant". [[User:Djbrasier|Djbrasier]] ([[User talk:Djbrasier|talk]]) 21:00, 26 August 2016 (UTC)

The teapot mention may just be a joke, not a reference.

Talk:1663: Garden

2016-04-04T13:56:39Z

141.101.98.114: /* Finally Garden is up on xkcd */

===Finally Garden is up on xkcd===
It is here the comic we have been waiting for, and it seems it is a April fool comic although it first came out past midnight in all of the US except Hawaii...
:I do not know when it will be on this page but for those impatient...
:[[File:Garden Loading screen shot.png]]
:It says to Relax, while it loads, but it will eventually get to a barren land with a growth lamp that can be moved:
:[[File:Garden Lamp screen shot.png]]
:The lamp can be moved and change color.
:[[File:Garden Red Lamp screen shot.png]]
:It may be there will be something growing if we wait long enough?
:And there will be more lamps and new items:
:[[File:Garden Three Lamp screen shot.png]]
:Yes he is messing with us for sure but at least not by not making a comic :-) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:46, 4 April 2016 (UTC)
::I succeeded to get a small plant, but I'm not sure how. --[[Special:Contributions/162.158.86.167|162.158.86.167]] 10:16, 4 April 2016 (UTC)
:::Try not to cover everything with every light wavelength. I'm sure you get different plants with different wavelengths:
:::[[File:aprilfool-2016-xorg.png]]
:::Also, I've noticed a constant cpu usage, indicating some kind of number crunching. The script's name "linden" reminded me of linden dollars and crowdsourcing bitcoin mining with javascript, but afair linden dollars were never mined nor based on cryptography. -- [[User:Xorg|Xorg]] ([[User talk:Xorg|talk]]) 10:30, 4 April 2016 (UTC)
::::"Linden" is probably a reference to the Linden trees, a genus (Latin name Tilia). It would make more sense than a reference to dollars, at least. [[Special:Contributions/162.158.135.57|162.158.135.57]] 12:14, 4 April 2016 (UTC)
:::Ok, it's *moving*. The leaves wobble in the wind. That explains the cpu usage. So far I have seen the following images: <code>asdfx2=""; for (asdfx in garden.linden.imgCache.imgs) { asdfx2 += asdfx+" "; } asdfx2

"http://xkcd.com/1663/art/background.png http://xkcd.com/1663/art/talltrunk-2.png http://xkcd.com/1663/art/shrub-8.png http://xkcd.com/1663/art/wavyplant-3.png http://xkcd.com/1663/art/turtle-1.png http://xkcd.com/1663/art/shrub-6.png http://xkcd.com/1663/art/birdbath.png http://xkcd.com/1663/art/cactus-2.png http://xkcd.com/1663/art/trunk-6.png http://xkcd.com/1663/art/branch-11.png http://xkcd.com/1663/art/branch-18.png http://xkcd.com/1663/art/woman-1a.png http://xkcd.com/1663/art/branch-21.png http://xkcd.com/1663/art/rover.png http://xkcd.com/1663/art/leaves-7.png http://xkcd.com/1663/art/leaves-6.png "
</code> -- [[User:Xorg|Xorg]] ([[User talk:Xorg|talk]]) 12:10, 4 April 2016 (UTC)

For those who are in https (with firefox for example) and don't see the "comic", there is mixed content. Click on the padlock on the up-left corner, then on the arrow, then "disable the protection against not secure elements" (or something like that). [[User:Seipas|Seipas]] ([[User talk:Seipas|talk]]) 11:32, 4 April 2016 (UTC)

The comic is finally here! ... but it won't load on my computer. Does anybody know what the problem might be or how I can fix it? [[User:Soad Kraken|Soad Kraken]] ([[User talk:Soad Kraken|talk]]) 12:45, 4 April 2016 (UTC)

Does not load (continually Loading...) on IE/FF/Chrome for me (in UK, non-https, ad-blockers turned off) any ideas?

Did someone try the debugmode?
:http://xkcd.com/1663/?debug#YourCode

It also logs data in the console
[[User:Magno|Magno]] ([[User talk:Magno|talk]]) 12:51, 4 April 2016 (UTC)

Post new images here: [[1663: Garden/Images]]. Anyone know what happens to the site, it looks really weird and it is difficult to use the site now. [[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 13:52, 4 April 2016 (UTC)