Why a button that says "do not press" is impossible to leave alone
A warning is also an instruction manual. Before the label, pressing the button was one of a thousand things you were not doing and had no opinion about. After it, pressing the button is a specific act with a stated consequence, and not pressing it is something you are now actively choosing. The label did not close the door. It pointed at the door and told you it was there.
Psychologists call the general version of this reactance: the reflex to reclaim a freedom the moment somebody takes it away. It does not require the freedom to be worth anything. This button offers nothing at all, which is what makes it such a clean demonstration. There is no prize, no score to beat and nobody watching. The only thing on the far side of the instruction is the answer to what happens if you ignore it, and that turns out to be enough.
It helps that the cost of finding out is one tap and the consequence is obviously survivable. A real warning carries real risk, so curiosity has something to weigh against. This one carries none. Curiosity meets no resistance, and the button gets pressed.
What actually happens when you press it
Every press advances a counter and plays the outcome sitting at that position. The first press plays the first outcome, the fortieth plays the fortieth. It is a script rather than a shuffle, so the sequence is identical for everyone, and the order is a design decision instead of an accident of chance.
Each outcome does three things: it changes the page in some visible way, it writes a line to the log beneath the button, and it replaces the remark under the counter with a comment on what you have just done. The log holds the five most recent lines, which is enough to see the shape of a run without turning the page into a transcript.
Your press count is kept in your own browser. Close the tab, come back next week, and the button carries on from where you left it. Nothing is sent anywhere, because there is nowhere to send it.
The forty outcomes, and why they are in that order
The first eight are deliberately disappointing. The button flinches. It changes its label to NO. The page tilts by about a degree. The colours shift, slightly. Anybody who presses once and leaves should come away feeling that almost nothing happened, because almost nothing did.
From nine to eighteen it stops being subtle. The colour drains out completely, the type turns to Comic Sans, the button prints itself backwards, and the text separates into its constituent colours.
Nineteen to twenty-eight move outwards from the button to the page around it. The button shrinks, then overcorrects and becomes enormous. The page begins to rotate. Gravity reverses. Everything slides towards the bottom of the box.
The last stretch is a run-up. The page is reduced to a wireframe, the lights go down, the whole layout leans over, and the fortieth press fires everything at once.
The order is carrying the joke. Randomised outcomes would deliver the same forty effects with none of the escalation, and escalation is the only reason pressing it forty times is a different experience from pressing it once. Past forty the outcomes begin recycling, and the button says so plainly rather than pretending there is more.
The fake endings
Three times during the run, the button announces that it has finished. At thirteen presses it declares itself disabled and thanks you for playing. At twenty-seven it claims to have run out of outcomes. At thirty-four it promises that this one is genuinely the last.
All three are lies. Each holds for about two and a half seconds before the button drops the act and admits it was lying. The joke only works because the lie is always about the button and never about your computer: it does not imitate a system error, a browser warning or a security alert, and it never claims anything is wrong with your device.
It is also never really disabled. The button stays pressable the whole way through, and it is never marked as disabled in the page markup, so anybody reaching this page with a screen reader is told what is actually true instead of being handed the gag as a fact.
Where the secret ending is
Press it fifty times.
Fifty is not arbitrary. By then the button has told you not to press it on fifty separate occasions, and ignoring an instruction fifty times in a row deserves some form of acknowledgement. What you get is a short ceremony, a different share card, and nothing else whatsoever. There is no unlock, no bonus mode and no reward, which is rather the point of it.
Presses past fifty fall through to the recycled outcomes like any other. The secret ending is the end of the written content, not the end of the button.
Nothing here breaks anything
Every effect on this page is a single CSS class applied to one wrapper element, and the next press takes it off again. That wrapper holds the button and the log and nothing else, which is why the site header, the footer and both advertising slots stay completely still no matter how badly the middle of the page is behaving. It is one rule, and it is not negotiable.
Nothing is downloaded. Nothing is installed. No setting on your device is read or altered. The page never impersonates an error message, a virus warning, or anything belonging to your operating system, and it never will, because a toy that frightens the person using it has stopped being a joke.
The only thing recorded anywhere is the number of times you have pressed it, and that lives in your browser rather than on a server. Clear your browsing data and the count goes back to zero along with everything else.
Questions people ask
What happens if I press the button?
Something different every time, in a fixed order. The first few presses barely react — the button flinches, changes its label, tilts a degree. After that it escalates: colours invert, the type turns to Comic Sans, gravity stops working, the whole page becomes a wireframe. There are forty scripted outcomes and a secret one.
How many outcomes are there?
Forty, plus a secret ending at press fifty. Once you pass forty the outcomes start recycling and the button tells you so rather than pretending otherwise. More batches are planned.
Is there a secret ending?
Yes, at press fifty. You were warned fifty times, so it seems only fair. It gets you a different share card and absolutely nothing else, which is the point.
Does it remember how many times I pressed it?
Yes. The count lives in your own browser, so you can close the tab and pick up where you left off. There is no account and no server. Clearing your browser data resets you to zero.
Does the button actually break anything?
No. Every effect is a CSS class on one wrapper element and the next press clears it. Nothing is downloaded, nothing is installed, no setting on your device is touched, and the page never pretends to be an error message or a system warning. It is a button that lies about itself and nothing more.
Why is there no sound?
There is, but it is switched off until you switch it on. A page that makes noise the moment you open it is a page you close on a train. The toggle sits under the button and it remembers your choice.
Is it safe to press fifty times?
It is safe to press it as many times as you like. Nothing accumulates, nothing stacks, and every outcome is undone by the one after it. The worst thing that happens is that you spend eight minutes on a red button.