<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://www.explainxkcd.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=172.70.230.172</id>
		<title>explain xkcd - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://www.explainxkcd.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=172.70.230.172"/>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php/Special:Contributions/172.70.230.172"/>
		<updated>2026-04-14T08:21:15Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:2927:_Alphabetical_Cartogram&amp;diff=341200</id>
		<title>Talk:2927: Alphabetical Cartogram</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:2927:_Alphabetical_Cartogram&amp;diff=341200"/>
				<updated>2024-05-02T20:30:40Z</updated>
		
		<summary type="html">&lt;p&gt;172.70.230.172: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--Please sign your posts with ~~~~ and don't delete this text. New comments should be added at the bottom.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
replaced incorrect explanation [[Special:Contributions/172.70.230.172|172.70.230.172]] 20:30, 2 May 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
replaced incorrect explanation [[Special:Contributions/172.70.111.45|172.70.111.45]] 17:17, 1 May 2024 (UTC)&lt;br /&gt;
Is it me or is Hawaii strangely bigger than california. {{unsigned|172.70.100.40}}&lt;br /&gt;
:I think he's only counting the land area. The area between the islands may be creating an illusion that Hawaii is bigger. It's hard to tell just by looking, does anyone have the tech to measure this? P.S. remember to sign... [[User:Barmar|Barmar]] ([[User talk:Barmar|talk]]) 14:11, 1 May 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
Im just wondering why Maine is still so big.... [[User:JushJosh|JushJosh]] ([[User talk:JushJosh|talk]]) 13:22, 1 May 2024 (UTC)Jush&lt;br /&gt;
:I know, right? That's what made me think it wasn't just a simple alphabetical listing. That, and Hawaii is bigger than Alaska, despite the fact that Alaska is substantially higher on the list. In fact, it even appears that Alaska is smaller than Maine! How did Randall decide on the sizes??? [[User:Pie Guy|Pie Guy]] ([[User talk:Pie Guy|talk]]) 16:01, 1 May 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
The sad part is that Rhode Island grew. [[Special:Contributions/172.71.31.139|172.71.31.139]] 14:01, 1 May 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
I believe it is some sort of ranking rather than swapping sizes as the chart suggests, as South Carolina appears to be smaller than normal (?) [[User:Primmy|Primmy]] ([[User talk:Primmy|talk]]) 14:56, 1 May 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
Poor Utah :( [[User:Z1mp0st0rz|If you click on this you will get a fun surprise]] ([[User talk:Z1mp0st0rz|talk]]) 15:15, 1 May 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
I believe the first paragraph is incorrect. I did a full comparison, and Texas shrank the most (dropping 41 places from size ranking to alphabetical ranking), while Connecticut as well as Delaware grew the most (each rising 41 places between the lists). [[Special:Contributions/172.71.255.28|172.71.255.28]] 15:40, 1 May 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
This map gives a lot more land to Mexico. [[User:Weslar|Weslar]] ([[User talk:Weslar|talk]]) 16:31, 1 May 2024 (UTC)&lt;br /&gt;
:Mexico is not represented at all in the map. And all states are much smaller than in reality (unless you have a very big monitor, c.f. [[2911]]) --[[Special:Contributions/172.71.160.32|172.71.160.32]] 12:30, 2 May 2024 (UTC)&lt;br /&gt;
:I think [[User:Weslar|Weslar]] is saying that Mexico gains land, since (historically) it has everything south of Arizona, New Mexico, and Texas. (Source: Just visited the Alamo a couple weeks ago, on an eclipse vacation...) So the fact that the states are smaller makes Texas bigger. ([[User talk:tr0gd0r|talk]])&lt;br /&gt;
&lt;br /&gt;
UNFORTUNATELY it seems that there are many errors in the actual relationship of sizes. I did a quick area take off of each state. These units are in miles using the real width of Colorado (since it is about the same place in the list) as the scale reference. https://imgur.com/a/hKIVjRZ. you can see immediately that Delaware and Alaska and Iowa are incorrect in the order.&lt;br /&gt;
&lt;br /&gt;
Ignoring the Errors in the map and Assuming We are keeping the total area of the US the same and scaling the new map based on this total... then Alaska loses the most land area ( approx 510,000 mi) and Alabama gains the most Land area  (156,000 mi). Looking at which state gained or lost the largest percentage of its land area shows that Minnesota is the least affected at only 4.6% or 4,200 mi and Wyoming is the most affected losing 98% of its land area or 95,000 miles.[[Special:Contributions/162.158.41.56|162.158.41.56]]&lt;br /&gt;
&lt;br /&gt;
As a Wyomingite, I can't complain.  We're still bigger than our population justifies.  (fun fact, we get two whole senators despite lacking the population to actually justify a single house member)[[Special:Contributions/172.68.34.59|172.68.34.59]] 17:08, 1 May 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
Alaska is STILL disproportionally small. [[User:Fabian42|Fabian42]] ([[User talk:Fabian42|talk]]) 17:24, 1 May 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
Utah is way too big (should be after Texas) and Idaho is too small (should be bigger than the Ms)&lt;br /&gt;
&lt;br /&gt;
Why the hell is Massachusetts so BIG?! [[User:Psychoticpotato|Psychoticpotato]] ([[User talk:Psychoticpotato|talk]]) 13:01, 2 May 2024 (UTC)&lt;br /&gt;
:To account for all its Mass. [[Special:Contributions/172.71.242.175|172.71.242.175]] 13:51, 2 May 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
I went further and measured the exact sizes of each state to the pixel: https://imgur.com/a/d6ruHvs really nerd sniped myself lol. The post includes excel screenshots as well as text, and the image I used at the bottom. Will explain methodology if anyone wants. Obviously all these discrepancies are due to the fact that the states actually have to fit together for the joke-map to work. [[User:Paintadot|Paintadot]] ([[User talk:Paintadot|talk]]) 13:48, 2 May 2024 (UTC)&lt;br /&gt;
:Having the pixel area for each state in the explanation would be really nice! Do you count the &amp;quot;border pixels&amp;quot; (or maybe half of them) to the pixel area? (not sure if that would be sufficient to have Alaska stay atop of Arizona ...) --[[Special:Contributions/172.71.160.32|172.71.160.32]] 14:39, 2 May 2024 (UTC)&lt;br /&gt;
::As drawn, the borders vary significantly in width. Usually 2 pixels wide, but often 3 or more. Between states, I divided them evenly to the best of my judgment. For the outer borders of the lower 48, Hawai'i, and Alaska, I added roughly one outer pixel. It's possible it could be done better, but it's kind of subjective anyway. Nevertheless it seems a lot of us agree that it's an interesting thing to try to measure. I imagine it was a lot of fun for Randall to try to balance his stated goal with keeping the shapes of the states more or less correct :) [[User:Paintadot|Paintadot]] ([[User talk:Paintadot|talk]]) 16:16, 2 May 2024 (UTC)&lt;br /&gt;
:I was going to take some time to establish 'drawn areas', myself (perhaps work out if it were contained area, 'hull' area, one-axis scale, etc) and add the likiest metric in the &amp;quot;Alphabetic&amp;quot; group of columns (remember to re-colspan!), but looks like like you've got that covered... [[Special:Contributions/172.71.102.254|172.71.102.254]] 15:10, 2 May 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
I modified the table to include the data I gathered (https://imgur.com/a/d6ruHvs). I hope that's okay. This is my first contribution ^^' [[User:Paintadot|Paintadot]] ([[User talk:Paintadot|talk]]) 16:15, 2 May 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
What definition of 'fair' is Randall using? --[[User:NeatNit|NeatNit]] ([[User talk:NeatNit|talk]]) 15:04, 2 May 2024 (UTC)&lt;br /&gt;
:{{wiktionary|fair#Adjective|Number 3}} [[Special:Contributions/172.71.102.254|172.71.102.254]] 15:10, 2 May 2024 (UTC)&lt;/div&gt;</summary>
		<author><name>172.70.230.172</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=2916:_Machine&amp;diff=339487</id>
		<title>2916: Machine</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=2916:_Machine&amp;diff=339487"/>
				<updated>2024-04-12T14:47:11Z</updated>
		
		<summary type="html">&lt;p&gt;172.70.230.172: minor grammer&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 2916&lt;br /&gt;
| date      = April 5, 2024&lt;br /&gt;
| title     = Machine&lt;br /&gt;
| image     = machine_2x.png&lt;br /&gt;
| imagesize = 740x740px&lt;br /&gt;
| noexpand  = true&lt;br /&gt;
| titletext = The Credible Machine&lt;br /&gt;
}}&lt;br /&gt;
* To experience the interactivity, visit the [https://xkcd.com/2916/ original comic].&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|Created by a WELL OILED ROBOT. Do NOT delete this tag too soon.}}&lt;br /&gt;
This 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.&lt;br /&gt;
&lt;br /&gt;
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 (see the [[#Trivia|trivia section]] below).&lt;br /&gt;
&lt;br /&gt;
This is a spin on the game {{w|The Credible Machine}}. The title text explicitly references this, albeit in a linguistic reversal.&lt;br /&gt;
&lt;br /&gt;
The comic starts in a main screen where the user can create a {{w|Rube Goldberg machine}} in a &amp;quot;Cell&amp;quot; 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&amp;lt;!-- that sort marbles by color SEEM TO 'RANDOMLY' REFRACT/DEFLECT, IF SORTING IS TRUE THEN EXPLAIN IN NEW/RELOCATED SECTION? --&amp;gt; (which deflect marbles) and fans (which blow marbles around), as well as decorative elements which have no effect on the balls.&lt;br /&gt;
&lt;br /&gt;
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 behaviour to account for this.&lt;br /&gt;
&lt;br /&gt;
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 colour 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.)&lt;br /&gt;
&lt;br /&gt;
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 neighbouring cells (which may be more sporadic then the feed you designed your cell with, and contain stray balls of different types). If any supplying-neighbours are still marked as &amp;quot;under construction&amp;quot;, they ''may'' provide the balls as if perfectly routed from their own (eventual) source, but will eventually dry up.&lt;br /&gt;
&lt;br /&gt;
It is unknown exactly how and why a particular submission becomes a permanent part of the grid&amp;lt;!-- conceivably many interesting criteria could be used *other* than pure randomness, but only the dev-team will know for sure; I doubt that the userbase can ever extract this information without access to the server-side code --&amp;gt;, 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 &amp;quot;Under construction&amp;quot; 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. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery heights=&amp;quot;200&amp;quot; widths=&amp;quot;150&amp;quot;&amp;gt;&lt;br /&gt;
File:2916_popup_intro.png|Introduction popup&lt;br /&gt;
File:2916_popup_time.png|Time limit popup&lt;br /&gt;
File:2916_popup_submit.png|Submission popup&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;UNDER CONSTRUCTION&amp;quot; as well as &amp;quot;DJIA ↑ 31415&amp;quot; once in each cell. &amp;quot;DJIA&amp;quot; stands for the Dow Jones Industrial Average, with &amp;quot;DJIA ↑ 31415&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Under construction cells will feed balls of the appropriate colour into neighbouring 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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 colour 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.&lt;br /&gt;
&lt;br /&gt;
===Toolbox items===&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin:auto&amp;quot;&lt;br /&gt;
|+ List of objects&lt;br /&gt;
|-&lt;br /&gt;
! Description !! Effect !! Image&lt;br /&gt;
|-&lt;br /&gt;
| Plank || Static || [[File:2916_plank.png|frameless|upright=0.25]]&lt;br /&gt;
|-&lt;br /&gt;
| Hammer || Static || [[File:2916_hammer.png|frameless|upright=0.25]]&lt;br /&gt;
|-&lt;br /&gt;
| Sword || Static || [[File:2916_sword.png|frameless|upright=0.25]]&lt;br /&gt;
|-&lt;br /&gt;
| Hinged scoop || Rotates around its hinge, tries to stay horizontal with a springy effect || [[File:2916_scoop.png|frameless|upright=0.25]]&amp;lt;br&amp;gt;[[File:2916_scoop_mirrored.png|frameless|upright=0.25]]&lt;br /&gt;
|-&lt;br /&gt;
| Anvil || Static || [[File:2916_anvil.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| Brick || Static || [[File:2916_brick.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| 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]]&lt;br /&gt;
|-&lt;br /&gt;
| Pillow || Balls will not bounce if they hit it || [[File:2916_pillow.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| 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]]&lt;br /&gt;
|-&lt;br /&gt;
| Attractor/Black Hole || Pulls balls toward center, can be resized || [[File:2916_attractor.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| Repulsor/White hole || Repels balls away from center, can be resized || [[File:2916_repulsor.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| Prism || &amp;quot;Refracts&amp;quot; balls as they enter and exit, causing them to curve to follow the color of the ball as much as possible{{Actual citation needed|...I can believe this might have been the intent, but I've never seen any such behaviour, even when dripping combined red and blue balls in from the same incident angle on the same spot, both types seem to take whatever exit they want, unpredictable and not at all differentiated between colours.}} || [[File:2916_prism.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| Wheel || Spins depending on arrow keys [right/left] pressed while selected (default:anticlockwise), deflects balls, can jam with enough resistance (e.g. glut of balls or against other elements). || [[File:2916_wheel.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| &amp;quot;Good job&amp;quot; trophy || Static || [[File:2916_trophy.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| Glass cup || Static || [[File:2916_cup.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| Cat || Swats away balls in front of itself (was added later) || [[File:2916_cat_new.png|frameless|upright=0.25]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin:auto&amp;quot;&lt;br /&gt;
|+ Characters&lt;br /&gt;
|-&lt;br /&gt;
! Description !! Image&lt;br /&gt;
|-&lt;br /&gt;
| Ponytail with raised arms || [[File:2916_ponytail_arms.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| Ponytail standing || [[File:2916_ponytail.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| Cueball with raised arms || [[File:2916_cueball_arms.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| White Hat || [[File:2916_whitehat.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| Knit Cap sliding, resting, or floating? Or sneaking, if rotated ~45 degrees || [[File:2916_knitcap_resting.png|frameless|upright=0.25]]&lt;br /&gt;
|-&lt;br /&gt;
| Knit Cap || [[File:2916_knitcap.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| Helmet? || [[File:2916_helmet.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| Probably Deterministic sign || [[File:2916_deterministic.png|frameless|upright=0.25]]&lt;br /&gt;
|-&lt;br /&gt;
| Squirrel || [[File:2916_squirrel.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| [[1682: Bun|Bun]] || [[File:2916_rabbit.png|frameless|upright=0.125]]&lt;br /&gt;
|-&lt;br /&gt;
| Cat || [[File:2916_cat.png|frameless|upright=0.125]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Other items===&lt;br /&gt;
&lt;br /&gt;
Ball containers at the bottom&lt;br /&gt;
{|&lt;br /&gt;
|[[File:2916_container_red.png|thumb|center|50px]]&lt;br /&gt;
|[[File:2916_container_yellow.png|thumb|center|50px]]&lt;br /&gt;
|[[File:2916_container_blue.png|thumb|center|50px]]&lt;br /&gt;
|[[File:2916_container_green.png|thumb|center|50px]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Cueball and Megan in the ''USS Buoyancy''&lt;br /&gt;
[[File:4d425c.png|thumb|left|150px]]&lt;br /&gt;
&amp;lt;br clear=all&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pit below the ''USS Buoyancy'' (not to scale)&lt;br /&gt;
[[File:2916_pit_bottom.png|thumb|left|300px]]&lt;br /&gt;
&amp;lt;br clear=all&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Color routing ===&lt;br /&gt;
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:&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
! Color&lt;br /&gt;
! Mass&lt;br /&gt;
! Density&lt;br /&gt;
! Restitution (bounciness)&lt;br /&gt;
! Linear damping (drag)&lt;br /&gt;
|-&lt;br /&gt;
! data-sort-key=&amp;quot;00F&amp;quot; | Blue&lt;br /&gt;
| 0.08&lt;br /&gt;
| 1&lt;br /&gt;
| 0&lt;br /&gt;
| 0&lt;br /&gt;
|-&lt;br /&gt;
! data-sort-key=&amp;quot;F00&amp;quot; | Red&lt;br /&gt;
| 0.08&lt;br /&gt;
| 1&lt;br /&gt;
| 0.8&lt;br /&gt;
| 0&lt;br /&gt;
|-&lt;br /&gt;
! data-sort-key=&amp;quot;0F0&amp;quot; | Green&lt;br /&gt;
| 0.75&lt;br /&gt;
| 9.325&lt;br /&gt;
| 0&lt;br /&gt;
| 0&lt;br /&gt;
|-&lt;br /&gt;
! data-sort-key=&amp;quot;FF0&amp;quot; | Yellow&lt;br /&gt;
| 0.024&lt;br /&gt;
| 0.3&lt;br /&gt;
| 0.6&lt;br /&gt;
| 2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
In order to maintain sufficient correct arrivals at exits&amp;lt;!-- and, I believe, sufficiently few ''wrong'' arrivals... does it enumerate the 'net correct delivery rate' to establish the validity of the output? ...needs more research --&amp;gt;, it may be necessary to add a method of filtering the hues.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- This may not be the most efficient depiction (with just four/less 'core methods', after following &amp;quot;See X/Y&amp;quot;s) but if the Prism or some other item actually adds zignificantly practical pre-&amp;quot;See&amp;quot; differences then the all-vs-all format (with the reversals/same-to-sames still there to be abbreviated/redirected) will come into its own.&lt;br /&gt;
If you so wish, redo. e.g. as &amp;quot;;header + :paragraph&amp;quot;s or table of &amp;quot;!Combo(s)!!Methodology&amp;quot;&lt;br /&gt;
NB:&lt;br /&gt;
  1x ! Row-start Style=                                                 | Row-start 'header'&lt;br /&gt;
  4x | *Unwikiparsable key just for editors' benefit* + optional Style= | Contents&lt;br /&gt;
...right now, I've mostly added &amp;quot;vertical fan&amp;quot; experiences (which I find useful for all but R/B differentiation), but more about bumpers (including fan-/wheel-collisions), the positive/negative 'force objects' and of course horizontal/angled fans could also be added.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! style=&amp;quot;background-color:black; color:white&amp;quot; | To separate !! style=&amp;quot;background-color:lightblue&amp;quot; | Blue !! style=&amp;quot;background-color:lightgreen&amp;quot; | Green !! style=&amp;quot;background-color:yellow&amp;quot; | Yellow !! style=&amp;quot;background-color:red&amp;quot; | Red&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;background-color:red&amp;quot; | Red&lt;br /&gt;
| *R/B* | '''Use 'bounce''''&lt;br /&gt;
The sole difference is how much balls will rebound from objects. Well managed and constrained ricochets should allow a sorting action.&lt;br /&gt;
| *R/G* | '''Use mass or 'bounce''''&lt;br /&gt;
Green balls cannot be levitated by a vertical fan. An incline across any such fan(s) will levitate only non-Greens.&amp;lt;br/&amp;gt;Green, like Blue, rebounds differently to Red. Green balls are also affected by black holes much less than all other balls.&lt;br /&gt;
| *R/Y* | ''See Y/B''&lt;br /&gt;
| *R/R* style=&amp;quot;text-align: center; background-color:black; color:white&amp;quot; | n/a &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;background-color:yellow&amp;quot; | Yellow&lt;br /&gt;
| *Y/B* | '''All methods'''&lt;br /&gt;
Yellow, alone, exhibits high drag against any unforced motion.&amp;lt;br/&amp;gt;It is also unique in all other ways; e.g. can be levitated highest, against all other hues (though most profoundly against Green).&lt;br /&gt;
| *Y/G* | ''See Y/B''&lt;br /&gt;
| *Y/Y* style=&amp;quot;text-align: center; background-color:black; color:white&amp;quot; | n/a&lt;br /&gt;
| *Y/R* style=&amp;quot;text-align: center; background-color:gray&amp;quot;  | ''See Y/B'' &amp;lt;!-- R/Y-&amp;gt;Y/B --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;background-color:lightgreen&amp;quot; | Green&lt;br /&gt;
| *G/B* | '''Use mass'''&lt;br /&gt;
Green balls cannot be levitated by a vertical fan.&amp;lt;br/&amp;gt;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).&lt;br /&gt;
| *G/G* style=&amp;quot;text-align: center; background-color:black; color:white&amp;quot; | n/a&lt;br /&gt;
| *G/Y* style=&amp;quot;text-align: center; background-color:gray&amp;quot;  | ''See Y/B'' &amp;lt;!-- Y/G-&amp;gt;Y/B --&amp;gt;&lt;br /&gt;
| *G/R* style=&amp;quot;text-align: center; background-color:gray&amp;quot;  | See R/G&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;background-color:lightblue&amp;quot; | Blue&lt;br /&gt;
| *B/B* style=&amp;quot;text-align: center; background-color:black; color:white&amp;quot; | n/a&lt;br /&gt;
| *B/G* style=&amp;quot;text-align: center; background-color:gray&amp;quot;  | See G/B&lt;br /&gt;
| *B/Y* style=&amp;quot;text-align: center; background-color:gray&amp;quot;  | See Y/B&lt;br /&gt;
| *B/R* style=&amp;quot;text-align: center; background-color:gray&amp;quot;  | See R/B&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
{{incomplete transcript|Do NOT delete this tag too soon.}}&lt;br /&gt;
&lt;br /&gt;
:[The placeholder image shows four balls, colored red, green, yellow and blue, bouncing on top of three white blocks. Text in the center: &amp;quot;[visit xkcd.com to view]&amp;quot;]&lt;br /&gt;
&lt;br /&gt;
:[Cueball with lab coat, intro popup]&lt;br /&gt;
:Cueball: Balls falling into your cell should be routed to the outputs at a steady rate.&lt;br /&gt;
&lt;br /&gt;
:[Cueball with lab coat, warning popup]&lt;br /&gt;
:Cueball: For security reasons, balls that remain in your device for more than 30 seconds will be removed and destroyed.&lt;br /&gt;
&lt;br /&gt;
:[Cueball with lab coat, submit popup]&lt;br /&gt;
:Cueball: Congratulations! Your contraption has passed all tests. Press [submit button] to submit it to be added to the machine!&lt;br /&gt;
&lt;br /&gt;
==Trivia==&lt;br /&gt;
*Randall acknowledges the people who helped him create this comic in a [[Header_text#Machine|comic-specific header text]]. &lt;br /&gt;
**With 11 different involved apart from Randall this is by far the comic with most people involved.&lt;br /&gt;
*Some hidden keyboard shortcuts have been found:&lt;br /&gt;
** Follow balls: Ctrl + Alt/Option + B (now also accessible by using the button provided)&lt;br /&gt;
** Show debug overlay: Ctrl + Shift + Cmd + D&lt;br /&gt;
** Delete selected item: Fn + Delete&lt;br /&gt;
*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!&lt;br /&gt;
**MACHINE&lt;br /&gt;
**Happy Belated April Fool's Day!&lt;br /&gt;
**This thus ends any discussion of whether this should be seen as an April Fool's comic or not. &lt;br /&gt;
**It just came out 4 days late. This has also happened several times since [[Garden]].&lt;br /&gt;
[[File:2916 Machine Facebook April fools' confirmation.png]]&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:April fools' comics]]&lt;br /&gt;
[[Category:Comics with color]]&lt;br /&gt;
[[Category:Dynamic comics]]&lt;br /&gt;
[[Category:Comics with animation]] &lt;br /&gt;
[[Category:Interactive comics]]&lt;br /&gt;
[[Category:Comics featuring Cueball]]&lt;br /&gt;
[[Category:Comics featuring Megan]]&lt;br /&gt;
[[Category:Comics featuring Ponytail]]&lt;br /&gt;
[[Category:Comics featuring White Hat]]&lt;br /&gt;
[[Category:Comics featuring Knit Cap]]&lt;br /&gt;
[[Category:Characters with hats]]&lt;br /&gt;
[[Category:Squirrels]]&lt;br /&gt;
[[Category:Buns]]&lt;br /&gt;
[[Category:Cats]]&lt;/div&gt;</summary>
		<author><name>172.70.230.172</name></author>	</entry>

	</feed>