<?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.69.194.141</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.69.194.141"/>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php/Special:Contributions/172.69.194.141"/>
		<updated>2026-04-17T11:13:10Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:2916:_Machine&amp;diff=339491</id>
		<title>Talk:2916: Machine</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:2916:_Machine&amp;diff=339491"/>
				<updated>2024-04-12T15:22:39Z</updated>
		
		<summary type="html">&lt;p&gt;172.69.194.141: Grumble about edit, or at least edit 'reason'.&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;
rather late for an april fools comic innit? also there doesn't seem to be anything exciting in this one lol, none of the usual cool exploration easter eggs, as far as i could tell at least [[Special:Contributions/172.71.178.76|172.71.178.76]] 16:41, 6 April 2024 (UTC)Erfaniom&lt;br /&gt;
:Randall posted an eclipse comic on Apr. 1. All April Fools comics are interactive. [[User:Z1mp0st0rz|Z1mp0st0rz]] ([[User talk:Z1mp0st0rz|talk]]) 15:27, 10 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
: We're exploring crowdsourced human creativity here, in a way, so it can be a lot more interesting then Randall's exploration comics, at least for me, because i did take two years of GCSE psychology and enjoyed it. [[Special:Contributions/172.64.238.130|172.64.238.130]]&lt;br /&gt;
&lt;br /&gt;
: looks like the egg's on my face lmao, i think i was among the first people to make anything, so everywhere was under construction for me, i didn't even understand that it was like a crowd thing [[Special:Contributions/172.70.210.52|172.70.210.52]] 14:19, 9 April 2024 (UTC)Erfaniom&lt;br /&gt;
&lt;br /&gt;
Just popped over using Chrome on Android and all I see is four &amp;quot;missing picture&amp;quot; logos spinning around, plus another down the bottom right... [[Special:Contributions/141.101.68.193|141.101.68.193]] 18:13, 6 April 2024 (UTC)&lt;br /&gt;
:Okay, followup: it behaves quite differently on the non mobile site. You get two entry points with red balls and yellow balls and you need to place the various gizmos to direct the balls to the correct exit point. Once enough have correctly passed to turn the red X into a green tick, you have the option to submit. If you do, once you have named your design it will be added to the grid with other submissions all of which exist to push red and yellow balls around. (if you come across &amp;quot;Memories of Ragnarok&amp;quot;, that's mine) [[Special:Contributions/172.71.134.207|172.71.134.207]] 18:27, 6 April 2024 (UTC)&lt;br /&gt;
::The number of inputs appears to vary between 1 and 4, each of a different color, with one color-coded output for each. [[User:Claire Kholin|Claire Kholin]] ([[User talk:Claire Kholin|talk]]) 18:49, 6 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
On the &amp;quot;machine&amp;quot; section, you see lots of &amp;quot;under construction cells&amp;quot;.  Perhaps this will develop as more are submitted.  I notice the &amp;quot;under construction tape&amp;quot; has &amp;quot;DJIA&amp;quot; and &amp;quot;31415&amp;quot;,  perhaps a reference to &amp;quot;dow jones industrial average&amp;quot; and the first five digits of pi.  [[User:Zeimusu|Zeimusu]] ([[User talk:Zeimusu|talk]]) 18:37, 6 April 2024 (UTC)&lt;br /&gt;
:Whenever someone submits a cell, it fills in one of the under construction cells. [[User:Claire Kholin|Claire Kholin]] ([[User talk:Claire Kholin|talk]]) 18:49, 6 April 2024 (UTC)&lt;br /&gt;
[Robert'); DROP TABLE Student!:;--] i just got a machine with 3 outputs one yellow another red and a third blue AND green and 3 inputs one green one blue and one red blue and yellow https://xkcd.com/2916/#xt=7&amp;amp;yt=50 hope its still there {{unsigned ip|172.70.115.173|18:01, 9 April 2024}}&lt;br /&gt;
:I think I just 'did' one with a Red+Yellow source (also separate singular Blue and Green) and a combined Blue+Green sink (and separate Yellow and Red). Got it working well, actually using fan-levitation to separate the R+Y enough to route them to their destinations, the Y then having to cross the occasional flying Green (which I was forced to &amp;quot;Bonk&amp;quot; and bounce up, entry being nearly at the bottom on right, exit being nearly at top on left) for its exit, everything else fairly simple. No idea if it got integrated, of course. Never seen any of my machines be accepted (when I later look around at what's there), so I'm still unsure if there's anything I can do to increase my chance of a successful square being made permanent on the grid.... [[Special:Contributions/172.70.163.49|172.70.163.49]] 20:58, 9 April 2024 (UTC)&lt;br /&gt;
:...still had it sitting there [https://imgur.com/kZdp3kH on my browser], though note that the Red+Yellow supply (mid-left) and the Green supply (right) aren't working here, through the &amp;quot;move the screen around, lose the feeds from 'Under Construction' squares&amp;quot; issue, or similar. But still I managed to submit it. The occasional Yellow and Red are falling from the Blue entrance in the top (I've not done anything special to filter those out/send them to a more proper exit, and it's too late to do so now anyway, it was just a Blue entry during the development process, of course).&lt;br /&gt;
:It's a pity you can't see it working, but I quite like my Yellow/Red separation. This might be the only time you see it in place, though, so a shame I didn't take a screenshot immedediately after submitting it. [[Special:Contributions/172.70.163.49|172.70.163.49]] 21:30, 9 April 2024 (UTC)&lt;br /&gt;
:I encountered a puzzle with five distinct pairs of in/out (none combined): Two blue, two red, one yellow.  It was difficult!  AFAIK five pairs is the highest reported so far.  When I submitted the solution to the Machine, it had Under Construction above and to each side, and (IIRC) empty below, and no balls were provided, alas.[[Special:Contributions/172.69.134.216|172.69.134.216]] 03:46, 12 April 2024 (UTC)&lt;br /&gt;
I wanted to add an image for each object, but do not have the necessary access, can someone who has access add the images that I linked in the table so they can be included? [[User:Claire Kholin|Claire Kholin]] ([[User talk:Claire Kholin|talk]]) 18:49, 6 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
I found a discussion with some guy talking about the API at https://euphoria.leet.nu/room/xkcd/ ; this could be useful for the wiki.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
[c+1] now time to try fucking with the api&lt;br /&gt;
[c+1] https://incredible.xkcd.com/&lt;br /&gt;
  [userwithnoaccount] 404&lt;br /&gt;
[c+1] it seems there are numbered machines under incredible.xkcd.com/machine/x&lt;br /&gt;
  [c+1] returns a grid of individual machinlets&lt;br /&gt;
  [c+1] which are uids like 3a7af27c-5389-5dcb-b660-3feab6be2ceb&lt;br /&gt;
  [c+1] they're stored at urls like incredible.xkcd.com/folio/3a7af27c-5389-5dcb-b660-3feab6be2ceb&lt;br /&gt;
  [c+1] there appear to be 33 machines total&lt;br /&gt;
  [c+1] the json it returns seems to refer to these as &amp;quot;versions&amp;quot;&lt;br /&gt;
  [c+1] $ curl -s https://incredible.xkcd.com/machine/21 | jq &amp;quot;.version&amp;quot;&lt;br /&gt;
        21&lt;br /&gt;
  [c+1] there is a machine/0, but it's all null&lt;br /&gt;
  [c+1] going to https://incredible.xkcd.com/machine/current redirects to the current machine&lt;br /&gt;
    [c+1] $ curl -sL https://incredible.xkcd.com/machine/current | jq &amp;quot;.version&amp;quot;&lt;br /&gt;
          35&lt;br /&gt;
[c+1] wait, is that the *total* number of mahcines?&lt;br /&gt;
[c+1] i would've thought there'd be more&lt;br /&gt;
[c+1] this whole think is rather esoteric&lt;br /&gt;
[c+1] Written in rust, too: https://rapier.rs/&lt;br /&gt;
[c+1] Uh oh.&lt;br /&gt;
      https://i.hypercone.us/?v=8e283d&lt;br /&gt;
  [c+1] HMMM&lt;br /&gt;
        https://i.hypercone.us/?v=079f8f&lt;br /&gt;
  [c+1] it seems there is no limit&lt;br /&gt;
  [c+1] i've uploaded a ~50M title&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Special:Contributions/172.70.57.146|172.70.57.146]]&lt;br /&gt;
&lt;br /&gt;
Had quite a lot of fun, added a few 'successful' machines to the grid. Noted that whenever I try to use the Prism that (after a short delay) the comic-pane blanks and I need to refresh the page/get a completely new 'challenge' to start from scratch, so I'm just not using the prism at all (used most of the other items, in combination or 'just the one across the whole board', whichever seems most fun). But it doesn't seem to do what I'd like it to do, which is sort multiple colours from the same inflow into different outflow directions. Which would be ''very'' useful in a 'crossroads' situation, the general solution of directing them cross-path being too prone to random collisions. Also might be useful in the 'submitted machine grid', as I note that errors propagate, whereas adding a filter on all inputs would clean out (dispose of/send off to a valid gate?) the rogue balls. Anyway, gonna have to come back to this later when there's more time... Maybe then I'll even have something useful to add to the Explanation. [[Special:Contributions/172.70.163.31|172.70.163.31]] 19:03, 6 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
The balls appear to be different weights. I just saw a machine that used fans to separate yellows from greens and blues in a sort of 'wheat from the chaff' manner to direct them to their correct outputs. I wonder what other hidden tricks are included. [[Special:Contributions/172.68.1.159|172.68.1.159]] 19:40, 6 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They're not all accepted, though it makes you think they are. Or something else more complex is going on we haven't realized yet. I made a machine that was working reliably, submitted it, and saw it on the overall grid. Reloading from a different browser I found the same location of the machine, with the same surroundings, but my machine had been replaced. It's nowhere else on the grid either. The first browser still shows it (but not after a reload with a cache clear). I'm not sure if there's some kind of &amp;quot;save&amp;quot; event that needs to happen beyond seeing your machine in the broader one, or if all user collaboration is an illusion, or if the system changes its mind about us somehow.&lt;br /&gt;
&lt;br /&gt;
: Yeah, i've been seeing this too. Please tell me if you find any of my machines, images at https://i.hypercone.us/?v=22d562 , https://i.hypercone.us/?v=ad8e3a , and https://i.hypercone.us/?v=8d4d6a . I want to be one of the few to have added Catalan and Spanish to the grid. [[Special:Contributions/172.71.134.164|172.71.134.164]] 20:56, 6 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
I've added some more observations to the page.  Also, a guess which is too uncertain to put on the main page: The ball launcher for the yellows on the far left side misses a lot, and the yellow container isn't the one on the left.  So I think the whole machine with crossing streams will result in the colors being sorted in their container order, and possibly have the streams combined and deposited at the bottom just above the containers.  --[[Special:Contributions/172.71.147.100|172.71.147.100]] 21:07, 6 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
has anyone seen the boat at the very bottom? [[User:Mushrooms|Mushrooms]] ([[User talk:Mushrooms|talk]]) 21:21, 6 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
trying to see it on Firefox for Ubuntu and it just tells me to &amp;quot;visit xkcd.com to view&amp;quot; - THAT'S WHERE I AM?! Tried clearing website data (but not my entire cache) and that didn't help.  Is there something I'm missing?&lt;br /&gt;
&lt;br /&gt;
Oooh, just had one with four ball-entries (four colours) and ''three'' exits (one caters for two arrows). Pity it's rather complicated to get entries to exits (even if I can merge two of the streams). Might have to give up on it, but I'd like to have seen how it fits in with the 'submited grid'. i.e. someone else gets a two-colour introduction spot. [[Special:Contributions/162.158.74.119|162.158.74.119]] 22:37, 6 April 2024 (UTC)&lt;br /&gt;
:Me again. I'm just refreshing the page, looking at the pattern of entries/exits (just a dozen or so screens in, getting some repeats of pattern, indicating that it's going back to tiles it was suggesting before, probably depends on how many others are contributing and extending...)&lt;br /&gt;
:Found another 'double-colour' example. Two yellows ''from the same side'', which probably means that there's a two-yellows been asked to exit from the neighbour (will check shortly).&lt;br /&gt;
:Quickly adapting from my spreadsheet notation, &amp;quot;R, Y, G, B&amp;quot; in order, each &amp;quot;(Entry, Exit)&amp;quot;, I've been using &amp;lt;dir&amp;gt; of L/R/T/B and a number (nominally percentage, though seems to include only values of 20, 30, 50, 70 and 80, so it ''might'' be more 1/6..5/6?) relating to the distance along from L to R (for T/B) or T to B (for L/R).&lt;br /&gt;
:This line is therefore (0,0)(L20+L70,R30+B70)(R80,L80)(T70,L50) ... no reds, two yellow pairings, a red pairing, a blue pairing. Would require at least two path-crossings (but I was going to calculate those things later, and double-colours might confuse my intended simple line-intersection calculation).&lt;br /&gt;
:...anyway, spent some time on this message, which might mean I'll get into a 'new batch' of available patterns as people have succeeded some of the challenges that I've been 'swiping left'. [[Special:Contributions/172.70.162.20|172.70.162.20]] 19:28, 7 April 2024 (UTC)&lt;br /&gt;
:...very next click: (0,0)(T30+L20,R20+R70)(R80,L80)(R50,B50), which is clearly the actual left-neighbour of the above. [[Special:Contributions/172.70.162.19|172.70.162.19]] 19:32, 7 April 2024 (UTC)&lt;br /&gt;
:Ok, stopped my refreshing to [https://imgur.com/a/OMFOmzy 'solve' a screen]. First of all I routed both yellows entries (right-upper and upper-right) to one yellow exit (middle-left) and gradually teased the greens across (lower-left to middle-right), as that way I was avoiding a criss-cross of balls, but the the other yellow exit (left-lower) was, of course, invalid.&lt;br /&gt;
:Changed it to drop one stream of yellows down towards the lower exit, across the rapidly firing greens (added a fan to filter away the occasional yellow that gets bounced over there, not much of an opportunity to filter falling-greens out of the yellow exit, so apologies to whoever gets the sceen below). Submited as &amp;quot;Two Yellows, One Green!&amp;quot;, whether or not that'll save (apparently, I should continue to contribute and not refresh/close, or else the server will not keep the solution?).&lt;br /&gt;
:Interestingly, all four adjacent tiles are &amp;quot;Under construction&amp;quot;, and if I scroll up... *DARN* the comic has blanked out (nothing there between the upper PREV/RANDOM/NEXT buttons and the lower ones, just whitespace). This may mean that it did not save. This is the kind of 'page crash' I get when I try using a Prism or get too many balls rattling around on top of a Black Hole. Perhaps it doesn't like that I'm scrolling into an Under Construction that shouldn't be there? (But then, why ''is'' it there?)&lt;br /&gt;
:Anyway, all extra information for everyone.&lt;br /&gt;
:I'll just refresh the page and go back and do some more entry/exit mapping, maybe? [[Special:Contributions/172.70.162.20|172.70.162.20]] 20:17, 7 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you combine a bunch of these silly claw things in the middle by just spamming it, it begins to lag and do some chaotic collisions, even without balls colliding on it. It's curious how it does that seemingly randomly though. I wonder how calculations are added and if there's a tiny sprinkle of RNG. (Also, errors occur and say something about damaging recursion in the Rust programming language, so I guess we know how it was made. It's also pretty weird how there's not a lot of opening combinations? It's possible that the machine loops over in chunks of gears or something (that's what I'll call them). ([[User talk:Leo|talk]]) 13:15, 7 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
If you place a black hole in the centre of a wheel, it makes the wheel behave unpredictably between resets. Sometimes it's almost normal, sometimes it's a lot faster than usual, and sometimes it's stopped but launches balls that touch it with extreme force. I was able to use this to submit a machine which didn't actually let a single ball through after being submitted. https://i.hypercone.us/?v=928bcd [[Special:Contributions/162.158.33.149|162.158.33.149]] 01:19, 7 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
The page says that (and I have taken note of) the ball hue is ''coded'' to certain values, but is there a logic to those values that might be derived from the colour (either as RGB triplet or HSV/other colourspace definition). For example, the two ball-types with zero green component in their makeup are 'unit density' (green is far heavier &amp;quot;green+red&amp;quot; is far lighter, so it's not a simple relationship, unless it converts from °hue, in some way) and the only secondary colour exhibits non-zero drag. There's the possibility that it just derived from &amp;quot;we need different properties, we need different colours, we have no reason to connect either with other deliberately&amp;quot; or even some non-mathematical symbology (fire=red, water=blue(?), earth=green, air(/sunlight?)=yellow). But it makes me wonder what combination of properties cyan/magenta balls might have, if added. (Or is the choice of those four colours constrained, anyway? Though R/G colorblindness is already something of an accessibility failure, if anyone suffers that.) [[Special:Contributions/172.69.194.205|172.69.194.205]] 17:02, 7 April 2024 (UTC)&lt;br /&gt;
:For color vision issues, on Mac, open System Preferences, select Accessibility, select Display (in the Vision group), select the Color Filters tab, select Enable Color Filters, then finally try the different filters in the Filter Type menu.  One of them should help make the colors distinct.[[Special:Contributions/172.69.134.216|172.69.134.216]] 03:40, 12 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
[https://pastebin.com/7PAiLnyF Python script to get the URL and title of each Cell in the current machine]&lt;br /&gt;
&lt;br /&gt;
[https://pastebin.com/xBhywGde Result of running that script at the moment] (encoded with ROT13 because pastebin wouldn't let me save it otherwise)&lt;br /&gt;
:has anybody at all whatsoever been able to find their creation using this API? [[User:Bellydrum|Bellydrum]] ([[User talk:Bellydrum|talk]]) 21:58, 7 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
[https://pastebin.com/jN5MP2za Result of running that script on the first 42 machines], at least on these it looks like the only difference is that one cell is added each time? [[Special:Contributions/172.71.99.195|172.71.99.195]] 17:22, 7 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
I've submitted four now, none of which was accepted. I tend to spend a lot of time getting them just right. Any hints as to what the acceptance criteria might be? Or do I just stink at this?&lt;br /&gt;
[[Special:Contributions/172.69.59.204|172.69.59.204]] 19:47, 7 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
There appears to be a new object: a cat that bats things that touch it.&lt;br /&gt;
[[Special:Contributions/172.69.214.39|172.69.214.39]] 20:17, 7 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
Is anyone else experiencing the bug where prisms cause the comic to disappear (leaving only the white background where it was) after a while? It makes viewing the whole machine basically impossible. (On further testing it appears to be firefox-exclusive.) [[Special:Contributions/172.70.162.38|172.70.162.38]] 20:31, 7 April 2024 (UTC)&lt;br /&gt;
:I've had the &amp;quot;Prisms break things&amp;quot; from the beginning (before any practical content). As in, trying to use them in a design breaks things. But I ''did'' glance upon their occasional use in the 'view submissions grid'. Right now I'm suffering from &amp;quot;white only&amp;quot; issue (see my &amp;quot;multi-yellow&amp;quot; accounts, above). I ''am'' using Firefox, if that's indeed relevant to this issue, but right now I'm not near any other up-to-date browser I care to use. [[Special:Contributions/172.70.163.31|172.70.163.31]] 21:37, 7 April 2024 (UTC)&lt;br /&gt;
:I'm getting the same issue with black holes (which probably makes more sense - put a black hole there and you'd expect everything else to disappear :o) - except that on one occasion I was able to put about 6 black holes in before the 7th one vanished everything.[[Special:Contributions/172.69.194.121|172.69.194.121]] 09:15, 8 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
Has anyone seen their own cell in the machine at all yet? A manual approval system is probably necessary for obvious reasons, but if so it does seem to be moving quite slowly.&lt;br /&gt;
[[Special:Contributions/172.69.65.24|172.69.65.24]] 02:58, 8 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
How on earth is everyone seeing different parts of the grid? If I request &amp;quot;view machine&amp;quot; I can only see my own square, and the edges of everyone elses. Nothing else, definitely not all of the machine. [[Special:Contributions/172.68.64.149|172.68.64.149]] 21:11, 8 April 2024 (UTC)&lt;br /&gt;
::You should be able to click and drag the view around. [[Special:Contributions/172.71.242.54|172.71.242.54]] 21:41, 8 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
Whoever designed the room entirely full of fans is evil - every time I scroll near it my entire browser freezes up and becomes unresponsive. And then the comic usually blanks.[[;8Special:Contributions/172.69.194.81|172.69.194.81]] 08:23, 9 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
None of [https://www.explainxkcd.com/wiki/index.php?title=2916:_Machine&amp;amp;diff=339487&amp;amp;oldid=339486 these edits] were anything to do with &amp;quot;grammar&amp;quot;, so why would anyone describe the change as such? The spelling of &amp;quot;colo(u)r&amp;quot; is an internationali[s|z]ation issue, of note, and why I usually prefer to defer to using words like &amp;quot;hue&amp;quot;, instead, in such contexts on this site. The change of the link from &amp;quot;The Incredible Machine&amp;quot; (where the page exists) to &amp;quot;The Credible Machine&amp;quot; (where it doesn't, because that's really just this comic's own joke) I aready changed back... If you think it doesn't properly explain the pun/negation, then rewrite; but don't make it an invalid link to something that doesn't even exist, as you'd know if you had even followed the link(s). [[Special:Contributions/172.69.194.141|172.69.194.141]] 15:22, 12 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Level scrolling bug ==&lt;br /&gt;
&lt;br /&gt;
When one views the whole machine, and scrolls down far enough, everything just disappears, and the comic is completely unresponsive. Has anyone else seen this? [[Special:Contributions/198.41.236.152|198.41.236.152]] 20:38, 7 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
:I'm now seeing the same issue, I wasn't before. (I'm using Chrome) [[Special:Contributions/172.70.162.20|172.70.162.20]] 21:06, 7 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
::A hard refresh appears to have fixed this for me (same person as above). [[Special:Contributions/141.101.99.101|141.101.99.101]] 10:28, 8 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
:I've been having this issue as well (I'm using firefox). Opening the site in Edge instead seemed to work around it for me, so it might only affect Firefox (and derivatives). [[Special:Contributions/172.70.163.31|172.70.163.31]] 21:27, 7 April 2024 (UTC)&lt;br /&gt;
::See also the 'firefox bug' comments currently immediately above this section. (Please don't ask me to start Edge up, I hate it, won't use it any more than the system requires me to...) [[Special:Contributions/172.70.163.31|172.70.163.31]] 21:37, 7 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
:Update - I did a hard refresh so I could play around with the new additions and I'm no longer encountering the bug, even on firefox. I think the &amp;quot;white screen&amp;quot; bug is fixed now and you just need to hard-refresh to download the fixed JS instead of using the cached one. (same person as 172.70.163.31 and 172.70.162.38) [[Special:Contributions/172.70.86.16|172.70.86.16]] 11:16, 8 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
==New Category: Ball Pit?==&lt;br /&gt;
&lt;br /&gt;
What do you think about a new category for comics with [[ball pits]]? [[150]], [[219]], [[485]], [[498]], [[2916]]? [[Special:Contributions/162.158.134.229|162.158.134.229]] 21:50, 7 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
[[:Category:Playpen balls]] already exists.&lt;br /&gt;
[[Special:Contributions/172.70.174.133|172.70.174.133]] 17:35, 9 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Prism Use? ==&lt;br /&gt;
&lt;br /&gt;
Can the prism be used to sort balls by color? (or in any other way that is useful and different?) [[Special:Contributions/172.68.34.61|172.68.34.61]] 12:11, 8 April 2024 (UTC)&lt;br /&gt;
:From what I've seen, no. Though may be ''extremely'' susceptible to incident angle. As far as my own use has been, they seem to randomise the trajectory (possibly also do a total-internal-reflection, I've had balls bounce around and exit at ''really'' weird angles), but it's hard to collimate a feed of balls into a single exact track, even straight down from a ceiling-feed (if you have a ceiling feed directly over the floor exit, lucky you, it'll still occasionally perturb balls off to the sides just enough to be bounced out as a gate-miss, unless you add 'funnel' architecture of one kind or another). Oh, and when balls do a lot of 'internal bouncing' it often forced me to reload the comic (overloaded the physics engine?), so could not continue to tweak the same design.&lt;br /&gt;
:On the other hand, perhaps this was the ''intent'', and just code/browser failings made it work erratically. Maybe would be an idea to go back and retest for this (anybody who can), do a little !!science!! to be recorded and explained on the page. [[Special:Contributions/172.69.43.183|172.69.43.183]] 12:51, 8 April 2024 (UTC)&lt;br /&gt;
:So, ive did some testing and found..nothing. i ''did'' find some uses for the prism though. Like outting them diagonally makes the balls follow a &amp;quot;path&amp;quot;, speeding up more and more (not really that great but it works with yellows), and that any ball hitting the left edge will try to go the the right edge. Not sure what else it can do, though. [[User:Begocc|Begocc]] ([[User talk:Begocc|talk]]) 09:35, 10 April 2024 (UTC)&lt;br /&gt;
::I did some thorough testing on a combined Red/Blue set of balls (carefully managed so that they were dropping into the target area as similarly as possible) and both rotated and moved the prism in various ways to check for any effects - like needing to enter parallel/perpendicular to the colour-bands, either to land on the 'target band' or start to pass across it, with the band then either facilitating or angling its 'fall through'. (Just visually checked, at first, then later adding 'buckets' below and to the sides, to try to catch balls departing on various trajectories in various 'clumps' making note of any that hit the 'bucket'-boundaries and bounced off elsewhere.)&lt;br /&gt;
::I found no significant sorting, and some balls would jitter around so much (within the prism) that they even launched almost straight back up where they came from (less poerfully than a Bonk-buffered ball, but not far off - also not reliable enough to use as a ball-elevator).&lt;br /&gt;
::In my experience, Yellow-sorting is easy (even against Blue and/or Red) by other means. Green is the easiest to have everything else sorted ''from'' (because it resists the fan method). The hardest to unmix are Reds from Blues, which one might think ''should'' be the most prism-differentiated but I'm afraid I just can't invoke that. Easier to have them fall a long way then bounce off a suitable bit of 'furniture', I can then get them to distribute ''fairly'' distinctly in two handy recepticles/onward-feed-hoppers, though it does need some careful placement of items to do it justice. It appears that none of my designs have made it to the 'public wall', but I have made a submitable machine or two that does such sorting sufficiently successfully to send it out (theoretically) to be seen.  [[Special:Contributions/172.70.163.30|172.70.163.30]] 11:38, 10 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Bugs and Exploits ==&lt;br /&gt;
&lt;br /&gt;
You can use a sword to break the physics on the hinge thingy and create your very own &amp;quot;magnetic hill&amp;quot;: https://imgur.com/a/IRZ0AlL [[Special:Contributions/162.158.134.108|162.158.134.108]] 13:02, 8 April 2024 (UTC)&lt;br /&gt;
:Hard to tell from that what other fans (perhaps) you've got completely off-clip.&lt;br /&gt;
:Those hinge-thingies can definitely be shifted by horizontal (outwith ball-weight pressures), but I've not found them to be reliable components as the &amp;quot;Stop&amp;quot; button (ball reset) seems to let those 'hinges' slring back to level, which might need a re-reset by moving them back past the thing that's holding them off-level.&lt;br /&gt;
:I have tried a few things with them:&lt;br /&gt;
:*'Ticker' mechanism, almost like a clock escapement, nudged by the rotating 'waterwheel', perhaps to try to release balls through a stream of other balls whilst keeping the path clear of collisions for each set, in turn.&lt;br /&gt;
:*'Batch dumper', accumulating a number of balls (above the 'hinge', behind a vertical bulkhead) until there's weight enough to 'open the hatch' and roll them out. (Again, an attempt to reduce collisions, by clumping batches together).&lt;br /&gt;
:*Finely configured inclines, by shoving something up into a free end of hinge with better angular resolution (but, as mentioned, this doesn't seem to want to 'hold', so probably would fail upon submission).&lt;br /&gt;
:...I had wondered if there was supposed to be a &amp;quot;falling anvil creates a catapult/ballista&amp;quot; idea behind the piece, but we don't ''have'' falling anvils (and definitely not in a repeating manner), and ball-powered catapult (esssentially &amp;quot;clown/acrobat jumps on one end of seesaw, clown/acrobat on other end flies up into the air&amp;quot;) also doesn't seem practical.&lt;br /&gt;
:I'll try to recreate ''your'' design, work out if there's anything new about it, but right now looks like it's a fan-powered incline-raiser. [[Special:Contributions/172.70.162.38|172.70.162.38]] 14:23, 8 April 2024 (UTC)&lt;br /&gt;
:: No fans! Here's a wider view: https://imgur.com/a/xPJcsor&lt;br /&gt;
:: It survives the reset, because the balls falling on the lever push it down to the sword and it gets stuck there every time. But you need to place the sword just right to make the gravity bug happen. And even then it depends on the number of balls in some ways. [[Special:Contributions/172.68.243.27|172.68.243.27]] 14:46, 8 April 2024 (UTC)&lt;br /&gt;
::: I've replicated the &amp;quot;tip of sword grabs the 'hinge'&amp;quot; thing, which is very interesting, but not the anti-gravity effect. The movement still seems ''to me'' more like a fan's 'area of effect' thing, than a wonky sense of gravity, the way that the balls are rolling/resisting/interacting with each other. No, I can't see where you've 'hidden' the fan (and I'm sure that fans can't act across submission-grid-boundaries, which was my next guess), so it's a bit of a funny thing that you've got there. [[Special:Contributions/172.70.163.49|172.70.163.49]] 21:35, 9 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
On occasion, two balls will fall from the containers as a pair, as if glued together. When this happens, they float down as if under much lower gravity, and then suddenly explode violently away from each other.[[Special:Contributions/172.69.43.182|172.69.43.182]] 10:56, 10 April 2024 (UTC)&lt;br /&gt;
What contaniners?? [[Special:Contributions/172.70.110.252|172.70.110.252]] 14:58, 12 April 2024 (UTC)&lt;br /&gt;
== The USS Buoyancy ==&lt;br /&gt;
&lt;br /&gt;
Guys. The Buoyancy. She ''floats''. When all four sets of balls reach the ball pit there aren't further additions. The boat starts floating on them. I've been watching it for a while. It seems she moves left and will probably end up escaping the ball pit. [[User:DL Draco Rex|DL Draco Rex]] ([[User talk:DL Draco Rex|talk]]) 20:44, 8 April 2024 (UTC)&lt;br /&gt;
:Update: A new row spawned in and it reset just before the Buoyancy could escape. Here's a screenshot I grabbed a while before the reset, she'd moved further left by the time the reset occurred. https://imgur.com/gallery/8UCASCu [[User:DL Draco Rex|DL Draco Rex]] ([[User talk:DL Draco Rex|talk]]) 20:51, 8 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
Alright, I'm almost 100% of the time seeing Buoyancy sink. Yes, she *floats* at first. But as she drifts to the sides, instead of yellows going underneath, reds and greens pile on top. Then, as the balls under expire (90 second timeout), she will start to sink. Very consistent behavior over time.&lt;br /&gt;
[[User:Keybounce|Keybounce]] ([[User talk:Keybounce|talk]]) 19:20, 11 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
What is the Bouaancy i cant find it anywhere??? [[Special:Contributions/172.70.110.252|172.70.110.252]] 14:58, 12 April 2024 (UTC)&lt;br /&gt;
== Added key combinations, found in source ==&lt;br /&gt;
&lt;br /&gt;
ctrl+alt+b&lt;br /&gt;
ctrl+shift+option+d&lt;br /&gt;
wheel: arrow keys&lt;br /&gt;
&lt;br /&gt;
: Can you clarify what &amp;quot;option&amp;quot; is? I have tried alt, function, and &amp;quot;operating system&amp;quot;, and none are doing it.&lt;br /&gt;
It is alt [[Special:Contributions/172.70.110.252|172.70.110.252]] 14:58, 12 April 2024 (UTC)&lt;br /&gt;
== Fixed Number of Possible Machinelets? ==&lt;br /&gt;
&lt;br /&gt;
I was resetting my browser to try and find new machinelet configurations, but there seem to be fewer and fewer as the game progresses. Hypothesis: the 'under construction' machinelets are set, and once one of them gets approved and added to the grid, that specific configuration of entrances/exits can't show up again.&lt;br /&gt;
&lt;br /&gt;
== Advanced components? ==&lt;br /&gt;
&lt;br /&gt;
How does one get access to the full set of components to build from? I'm only given planks, mallets, swords, scoops, anvils, bricks and fans. I never get any pillows, bumpers, cats, stick figures et cetera. Do they need to be &amp;quot;unlocked&amp;quot; through some achievement, or what? [[Special:Contributions/162.158.222.102|162.158.222.102]] 11:04, 9 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
  This caught me for a while as well. I have since discovered that the tool box has a scroll bar and can be scrolled down; that's where the others are hiding.&lt;br /&gt;
::Invisible scrollbars – every GUI obfuscator's favorite tool for making users' lives harder. [[Special:Contributions/162.158.222.142|162.158.222.142]] 18:17, 9 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Limit of 100 components? ==&lt;br /&gt;
&lt;br /&gt;
Has anyone else seen this?  At some point I started getting a count &amp;quot;95 / 100&amp;quot; towards the bottom of the toolbar.  When it hits &amp;quot;100 / 100&amp;quot; the rest of the toolbar greys out, and I can't add anything more.  (I suppose the physics engine has to keep a ceiling on the number of possible interactions between components.) —[[User:Scs|Scs]] ([[User talk:Scs|talk]]) 11:53, 10 April 2024 (UTC)&lt;br /&gt;
:Yes, quite early on I was dealing with a quite simple 'drop from ceiling straight down to floor' setup. After adding just enough 'funnel' to deal with 'splatter', I then built a castle wall in the open space just to make it fun (with some figures on/below it, that I've also tried to decorate in later submissions), of the 'grey blocks'.&lt;br /&gt;
:I actually hit the 100/100 ''exactly'' as I placed my final intended block. (No doubt that it's easy to hit the limit by just overlapping things so you can't see most of them, and other 'useless' placement, too...) [[Special:Contributions/172.70.85.48|172.70.85.48]] 19:57, 10 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
== uss boyancy ==&lt;br /&gt;
&lt;br /&gt;
Why have i not been seeing any uss boyancy [[Special:Contributions/172.70.110.122|172.70.110.122]] 14:04, 10 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
Haha I dare you to go to https://xkcd.com/2916/#xt=7&amp;amp;yt=57 and stare at the two black holes next to eachother &amp;gt;:) [[User:Z1mp0st0rz|Z1mp0st0rz]] ([[User talk:Z1mp0st0rz|talk]]) 15:27, 10 April 2024 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Build a &amp;quot;working&amp;quot; machine from parts? ==&lt;br /&gt;
&lt;br /&gt;
Has anyone started working on this idea:&lt;br /&gt;
&lt;br /&gt;
Since any given machine segment seems to be saved, even if not in the final result, *and* since these segments are failing when combined in the whole, how about a &amp;quot;really working&amp;quot; machine that starts replacing failing segments when they jam or otherwise fail to work in the real machine?&lt;br /&gt;
&lt;br /&gt;
The idea being something like, start the machine. Watch the top row, and see where the parts are failing to pass balls properly after two minutes. Replace the segments that are failing/jaming/etc, and let the new part process balls.&lt;br /&gt;
&lt;br /&gt;
As you work your way down, over about 2 hours at the current size, you will eventually get a machine that properly sends balls down to the bottom, without jamming, without having to &amp;quot;pretend&amp;quot; that off-screen parts are working.&lt;br /&gt;
&lt;br /&gt;
I mean, it's not like a gigantic, 600 segment machine will overflow memory on modern 32gb systems, nor consume so much power that these big huge CPU's will fail, right?&lt;br /&gt;
There is a 100 piece limit sadly&lt;br /&gt;
[[User:Keybounce|Keybounce]] ([[User talk:Keybounce|talk]]) 17:41, 10 April 2024 (UTC)&lt;br /&gt;
ps.: Why do white holes, black holes, prisms, etc, cause problems on some machines like mine and not others?&lt;br /&gt;
&lt;br /&gt;
== Foreshadowing ==&lt;br /&gt;
&lt;br /&gt;
I think that this Machine comic / game is foreshadowed by comic # 2785 titled Marble Run. {{unsigned ip|172.70.130.120|22:15, 11 April 2024}}&lt;/div&gt;</summary>
		<author><name>172.69.194.141</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=2916:_Machine&amp;diff=339472</id>
		<title>2916: Machine</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=2916:_Machine&amp;diff=339472"/>
				<updated>2024-04-12T09:50:18Z</updated>
		
		<summary type="html">&lt;p&gt;172.69.194.141: /* Explanation */&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 Incredible 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 colour. However, some outputs accept multiple colours, indicated by a double arrow, and some inputs produce multiple colours. 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 colour that passes through an exit, and reduces when no balls pass through, or if balls of the wrong colour 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;
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.&lt;br /&gt;
&lt;br /&gt;
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.&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 themself (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 in 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.69.194.141</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=2918:_Tick_Marks&amp;diff=339371</id>
		<title>2918: Tick Marks</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=2918:_Tick_Marks&amp;diff=339371"/>
				<updated>2024-04-11T13:30:26Z</updated>
		
		<summary type="html">&lt;p&gt;172.69.194.141: /* Explanation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 2918&lt;br /&gt;
| date      = April 10, 2024&lt;br /&gt;
| title     = Tick Marks&lt;br /&gt;
| image     = tick_marks_2x.png&lt;br /&gt;
| imagesize = 292x276px&lt;br /&gt;
| noexpand  = true&lt;br /&gt;
| titletext = If you're really savvy, you can hide an entire set of illicit transactions by timing them to draw what looks like a graph inset.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|Created by a BOT WORKING IN SECRET - Please change this comment when editing this page. Do NOT delete this tag too soon.}}&lt;br /&gt;
&lt;br /&gt;
This comic provides the reader with a suggestion on how to &amp;quot;conceal activity&amp;quot; — specifically, in this case, activity happening after what should have been the deadline for completing it — that is going to be graphed over time, by timing bursts of activity with the ticks on the time axis. This is assuming that the scale of the time axis is known, and that the &amp;quot;bottom&amp;quot; of the graph coincides with the line on which the ticks are drawn, rather than the &amp;quot;peak&amp;quot; of the largest tick.&lt;br /&gt;
&lt;br /&gt;
Theoretically, the graphed &amp;quot;activity&amp;quot; would be concealed behind the ticks, meaning anyone reading the graph would perceive activity as having ceased at the deadline, even though it had continued in time-axis-tick-sized bursts afterwards.&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[A graph with two axes is shown. Each axis has tick marks with every fourth mark a bit longer than those in between. The Y-axis is labeled with text rotated 90 degrees clockwise. There is no label on the X-axis. The graph is a jagged curve with three clear peaks; the area beneath the curve is shaded in light gray. After the third and highest peak the curve drops to zero. At the point of decline, a dotted line goes up to a label above the last peak. To the right of this dotted line, the X-axis and the ticks on it are clearly thicker than the axis and the ticks to the left.]&lt;br /&gt;
:Y-axis: Activity&lt;br /&gt;
:Label: Deadline&lt;br /&gt;
&lt;br /&gt;
:[Caption beneath the panel:]&lt;br /&gt;
:If you need to conceal activity, try timing it to hide behind the tick marks on the graph axis.&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Line graphs]]&lt;/div&gt;</summary>
		<author><name>172.69.194.141</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:36:_Scientists&amp;diff=334342</id>
		<title>Talk:36: Scientists</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:36:_Scientists&amp;diff=334342"/>
				<updated>2024-02-06T11:17:47Z</updated>
		
		<summary type="html">&lt;p&gt;172.69.194.141: 'unsigned'ing, and changing the reply-indent method...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If Cueball's a scientist, the statement is perfectly valid. Even more so if his scientist friends are helping him, and they can't find his shoes either. [[User:Davidy22|&amp;lt;u&amp;gt;&amp;lt;font color=&amp;quot;purple&amp;quot; size=&amp;quot;2px&amp;quot;&amp;gt;David&amp;lt;/font&amp;gt;&amp;lt;font color=&amp;quot;green&amp;quot; size=&amp;quot;3px&amp;quot;&amp;gt;y&amp;lt;/font&amp;gt;&amp;lt;/u&amp;gt;&amp;lt;sup&amp;gt;&amp;lt;font color=&amp;quot;indigo&amp;quot; size=&amp;quot;1px&amp;quot;&amp;gt;22&amp;lt;/font&amp;gt;&amp;lt;/sup&amp;gt;]][[User talk:Davidy22|&amp;lt;tt&amp;gt;(talk)&amp;lt;/tt&amp;gt;]] 07:07, 31 October 2012 (UTC)&lt;br /&gt;
&lt;br /&gt;
I found the fact that the last sentence was present in the explanation funnier than the comic itself. -- [[Special:Contributions/131.175.28.142|131.175.28.142]] 22:13, 14 May 2013 (UTC)&lt;br /&gt;
&lt;br /&gt;
Its worth pointing out the comic was drawn in 2006 -- 'pretty gay' was not nearly as politically incorrect then as it is now. Wow, this is an old comic. [[Special:Contributions/162.158.255.125|162.158.255.125]] 14:33, 8 September 2015 (UTC)&lt;br /&gt;
&lt;br /&gt;
Political incorrectness is a good thing. I'd hope he'd do this one again today. — [[User:Kazvorpal|Kazvorpal]] ([[User talk:Kazvorpal|talk]]) 01:07, 24 April 2019 (UTC)&lt;br /&gt;
:Political incorrectness is a good thing? wow. While I also find overly political correctness in many cases over the top, unneccesary and annoying, this is a clear example where political correctness helps to battle discrimination. By using the term &amp;quot;gay&amp;quot; to describe one stereotype associated with homosexuality, this stereotype is further enforced, and people are treated according to it. I do not know a lot about you, but your username sounds like an adjective, so imagine, I started a trend describing people who are e.g. pedophile as &amp;quot;kazvorpal&amp;quot;, and this trend catches on. Soon you would find yourself excluded from events, jobs, etc. because people would assume you are a pedophile. Wouldn't you prefer that to not happen? that is one example why political correctness is a good thing. Sorry for the trollfeeding. --[[User:Lupo|Lupo]] ([[User talk:Lupo|talk]]) 06:04, 24 April 2019 (UTC)&lt;br /&gt;
::No, you are suffering from the ravages of inductive reasoning. Political correctness includes a pretense that the speaker is battling discrimination, but it's just virtue signalling. They are, in fact, ''encouraging'' discrimination, and heaping advocacy of censorship and repression on top of it. Using &amp;quot;gay&amp;quot; as a mock pejorative does nothing to harm actual homosexuals, and in fact robs the term of its emotional power, as humor often does. Daniel Tosh incessantly making faux-bigoted comments uses humor to weaken racism, sexism, et cetera. And the end does not justify the means: Repressing the expression of others is evil, even when you're trying to use doing so to impress others about how virtuous you are. — [[User:Kazvorpal|Kazvorpal]] ([[User talk:Kazvorpal|talk]]) 15:43, 29 October 2019 (UTC)&lt;br /&gt;
::: That opinion is what scientists call &amp;quot;pretty straight white man&amp;quot;. --[[Special:Contributions/141.101.99.163|141.101.99.163]] 22:18, 2 March 2021 (UTC)&lt;br /&gt;
:::: Ad hominem {{unsigned|108.162.237.191}}&lt;br /&gt;
::::: Ad heteronym. Seriously though, stop being so ''straight'' --[[Special:Contributions/162.158.134.63|162.158.134.63]] 21:12, 4 May 2022 (UTC)&lt;br /&gt;
&lt;br /&gt;
as someone who scientists are calling &amp;quot;pretty gay&amp;quot; (bisexual) and &amp;quot;retarded&amp;quot; (autistic), I find this comic humorous. -- [[User:Arthur101|Arthur101]] ([[User talk:Arthur101|talk]]) 00:33, 11 October 2023 (UTC)&lt;br /&gt;
:- also gay and autistic here.  I agree this comic is funny, but that doesn't make it at all okay to use gay as an insult, or to use the r-slur at all, and I hope that basic level of &amp;quot;political correctness&amp;quot; becomes more common and respected (user: human physics padawan) {{unsigned ip|172.70.46.136|09:17, 6 February 2024}}&lt;br /&gt;
&lt;br /&gt;
Interesting edit I just felt I had to make, in response to another. The sentence:&lt;br /&gt;
 However, since their being scientists is irrelevant to the legitimacy of their opinions about Randall's shoe problems, presenting their teasing as an expert opinion is humorously misleading; a similar joke is at play in [[1206: Einstein]].&lt;br /&gt;
...a change of &amp;quot;their being&amp;quot; was changed to &amp;quot;there being&amp;quot;, assuming a homophonic error.&lt;br /&gt;
&amp;lt;br /&amp;gt;However, technically (at least idiomatically) all three &amp;quot;their/there/they're&amp;quot; ''could'' be correct.&lt;br /&gt;
*&amp;quot;their being scientists&amp;quot; - 'the state of being scientists that they possess' works well as a concept,&lt;br /&gt;
*&amp;quot;there being scientists&amp;quot; - 'that scientists exist in that situation' also does, somewhat&lt;br /&gt;
*&amp;quot;they're being scientists&amp;quot; - 'it is scientists that they be' works well ('that they are' in alternate grammatical dialect, but off the 'being' form in both cases, rather than the secondary contracted 'are')&lt;br /&gt;
Anyway, I changed it onwards to &amp;quot;them being&amp;quot;, i.e. 'those people (...that we can describe as scientists)'. In leiu of ''totally'' rewording to remove this (rather interesting) issue of grammar. [[Special:Contributions/172.70.85.147|172.70.85.147]] 11:33, 26 November 2023 (UTC)&lt;/div&gt;</summary>
		<author><name>172.69.194.141</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1075:_Warning&amp;diff=334225</id>
		<title>Talk:1075: Warning</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1075:_Warning&amp;diff=334225"/>
				<updated>2024-02-05T11:29:50Z</updated>
		
		<summary type="html">&lt;p&gt;172.69.194.141: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;And also that riding in a car is one of the most hazardous activities possible, and people don't realize this, the common view is that walking or riding in a plane is more dangerous when really being in a car is by several orders of magnitude. [[Special:Contributions/75.103.23.206|75.103.23.206]] 20:51, 7 December 2012 (UTC)&lt;br /&gt;
&lt;br /&gt;
This comic is actally a great justification for repealing all those annoying safety laws. --[[User:Qwach|Qwach]] ([[User talk:Qwach|talk]]) 05:43, 1 September 2013 (UTC)&lt;br /&gt;
&lt;br /&gt;
I have reworded the explanation (which said evolution had not prepared us for the modern world 'yet'). That implies that we are part-way along an evolutionary process that will see us well suited to motor vehicle travel in the forseeable future, which is not the case and which I don't think was intended by the comic. The sort of evolutionary adaptations required to make us fairly well suited to motor vehicle travel (as opposed to being well suited to walking around all day picking berries and spearing things, as we are now) would take at least several million years, and I think it is extremely unlikely we will still be driving around on highways in cars by then. So there will never be a successor species to the human that is adapted to motor vehicle travel. The main problems with us and cars are (1) reaction time, (2) durability in high-speed impacts and (3) a metabolism that is not adapted to sitting on our backsides whenever we want to get anywhere. For the past 3.5 billion years, none of our ancestors ever had to respond to mishaps at any faster than about 20km/h (running flat out). While our common ancestor with the chimpanzees was probably much better at surviving falls from heights than we are, surviving a collision at highway speeds is not something any of our ancestors ever had to do (at least not often enough to be adapted to it - they weren't adapted to occasional falls from very high cliffs either). Fast vehicles have only appeared in the last couple of hundred years and I would expect it to be many tens or hundreds of thousands of years before these new selection pressures make any noticable (although even then quite inadequate) difference to human physiology. So a very long-winded comment I know, but I hope it will give some perspective. [[User:Tarkov|Tarkov]] ([[User talk:Tarkov|talk]]) 09:34, 1 January 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
I do not think this comic is actually about cars (or other modes of transportation at all, really) but more about the great (and becoming greater still over time) divide between our biological evolution against our cultural, technological and governing ones and how we are not prepared to deal with this big mess that it creates in it's wake. [[User:Ragnarok700|Ragnarok700]]&lt;br /&gt;
[[Special:Contributions/108.162.241.8|108.162.241.8]] 22:26, 14 January 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
To be hoenst I think we'd reach a point where motor transport is as safe as we can possibly make it, or completely redundant, long before we evolve to suit it.[[Special:Contributions/108.162.248.24|108.162.248.24]] 04:08, 30 January 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
Didn't it evolve box-like exoskglotons after the evolutions Airton Senior made dying?&lt;br /&gt;
Or was it designed to thwart any blamgamesmanship?[[User:Weatherlawyer| I used Google News BEFORE it was clickbait]] ([[User talk:Weatherlawyer|talk]]) 18:28, 21 January 2015 (UTC)&lt;br /&gt;
&lt;br /&gt;
I changed the bit talking about the &amp;quot;next five miles&amp;quot; because it didn't make sense. When that is on a sign it's talking about the area in which the sign is talking about, not the fact that the driver will be going five more miles. -Pennpenn [[Special:Contributions/108.162.250.155|108.162.250.155]] 03:41, 16 February 2015 (UTC)&lt;br /&gt;
&lt;br /&gt;
Vehicles fast enough to injure people crashing in them or falling off them (e.g., chariots) have existed for several thousand years. Still, that's not long enough for significant evolutionary adaptation. [[User:Gmcgath|Gmcgath]] ([[User talk:Gmcgath|talk]]) 21:42, 17 December 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Why is this comic in the basketball category? [[User:Herobrine|Herobrine]] ([[User talk:Herobrine|talk]]) 00:23, 4 May 2019 (UTC)&lt;br /&gt;
&lt;br /&gt;
This whole discussion is moot as we have self-driving cars now :P [[User:The Cat Lady|-- The Cat Lady]] ([[User talk:The Cat Lady|talk]]) 12:57, 4 September 2021 (UTC)&lt;br /&gt;
:''Allegedly'' have self-driving cars. [[User:Firestar233|guess who]] ([[User talk:Firestar233|if you want to]] | [[Special:Contributions/Firestar233|what i have done]]) 08:05, 5 February 2024 (UTC)&lt;br /&gt;
:&amp;quot;Have ''allegedly'' self-driving cars&amp;quot; would work best, for the point I think you're making. ;) [[Special:Contributions/172.69.194.141|172.69.194.141]] 11:29, 5 February 2024 (UTC)&lt;/div&gt;</summary>
		<author><name>172.69.194.141</name></author>	</entry>

	</feed>