White House 'Build the Wall' Game Pulled: A Clone-Risk Lesson

The White House pulled its "Build the Wall" game after the Tetris Company complained about copyright, and the whole episode lasted about as long as a bathroom break. TechCrunch reported on 8 September 2026 that the page at whitehouse.gov/arcade/ now returns a 404.

I don't care much about the politics here. I care that a project shipped by the most-scrutinised web team on earth got killed by an IP problem that a five-minute review would have caught. That mistake is available to all of us for free.

---

🧱 What actually got taken down

The facts, as reported:

• The game was a block-stacking arcade thing on the White House site: pieces of various shapes fall, you stack them into a wall, framed as defence against a "zombie border siege."
• The Tetris Company posted on Instagram that it had nothing to do with making it, and said it takes "copyright infringement very seriously."
• Kotaku first spotted that the game had vanished. The URL 404s now.
• A second game, "Rio Run", is reportedly still up. The games drew wide criticism as racist, which is its own conversation and not the one I'm having today.

Note on causation: nobody has published a legal notice. A rights holder posted on social media and the page went away. That is a sequence, not proven cause and effect. Keep the two apart when you tell this story.

---

⚖️ Mechanics are free, the look is not

This is the part most self-taught developers get backwards. You are generally allowed to clone the rules of a game. You are on much thinner ice cloning the expression built on top of those rules. A US federal court made roughly that distinction against a Tetris clone back in 2012 (look up Tetris Holding v. Xio Interactive if you want the actual reasoning, not my paraphrase).

Rough map of where the risk sits:

Element	Typical exposure	Why
Core rules and mechanics	Low	Ideas and systems generally aren't copyrightable
The name "Tetris"	Very high	Registered trademark, near-zero defence
The seven distinctive falling shapes, in those colours, at that board ratio	High	Reads as protected expression, not a bare idea
Sprites, music, fonts ripped from the original	Very high	Straight copying of fixed works
Your own art on borrowed mechanics	Low–moderate	The usual indie path
"It's satire / commentary"	Unpredictable	A defence you argue in court, not a shield you ship with

Key takeaway: you can rebuild the mechanic. You cannot borrow the identity. If a player would name the original from a screenshot with the title cropped out, you've copied expression, not an idea.

---

🚨 The leverage isn't legal, it's your traffic

Here's the uncomfortable bit for anyone building in public. Nothing about that game got more infringing on the day it was noticed. What changed was attention.

Your takedown risk is roughly:

risk ≈ (how recognisable the borrowed thing is)
      × (how visible you are)
      × (how much the rights holder has to lose by ignoring you)

A clone with 12 monthly visitors survives for years. The same clone at the top of Hacker News, or on a government domain, gets one working day. Success is the trigger. So the honest question during a build isn't "will anyone notice?" It's "what happens to this project on the day it works?"

This is exactly why I refuse to build YouTube, Instagram or TikTok downloaders on induwara.lk, even though the keyword volume is enormous and the code is trivial. The traffic that makes such a tool worth building is the same traffic that ends the whole domain. I'd rather ship 250 boring calculators that nobody can take from me.

---

🛠️ A pre-ship IP check that costs you ten minutes

For a Sri Lankan student or a two-person team with no lawyer on retainer, this is the whole process:

1. Name check. Search your product name plus the word "trademark." If a company sells something under that name in your category, rename now. Renaming pre-launch is free; renaming after you rank is not.
2. Asset provenance. Every image, font, sound and icon needs a traceable licence. "Found it on Google" is not provenance. Write the source into a CREDITS.md while you add the file, not later.
3. AI-generated code and art. If a model wrote it, know who carries the risk if a claim lands. Providers differ a lot, and most protection is conditional on things like leaving safety filters on. I built the AI copyright indemnity checker precisely because those terms are unreadable otherwise.
4. Model licences, if you self-host. Llama, Gemma, Qwen and friends are not uniformly "free for commercial use" — some carry user caps and attribution clauses. The LLM licence checker covers the current terms.
5. The screenshot test. Show one screenshot to a friend with the title hidden. If they name someone else's product, redesign.
6. Have a kill switch. A feature flag or config row that disables one route without a rebuild. The difference between a bad afternoon and a bad quarter is how fast you can comply while you think.

Stage	Cost of fixing an IP problem
Before first commit	Free
Before launch	An afternoon
After it ranks	Your traffic, and possibly the domain

---

💡 What this means for you

Ship fast. Genuinely. Nobody in Sri Lanka is going to out-fund their way to an audience, so speed and specificity are the only real advantages available. But "move fast" has to include the ten minutes above, because IP is one of the few build mistakes you cannot patch after the fact. A bug you fix on Monday. A trademark problem takes your URL with it.

Three things I'd take from this:

• Clone the idea, never the identity. New name, your own art, your own board.
• Assume you'll be noticed on your best day. Design as if the traffic arrives, because the plan only fails when it works.
• Write down where every asset came from, at the moment you add it. Future-you cannot reconstruct it.

The White House had lawyers, a comms team and the most-watched domain in the world, and still put a Tetris-shaped thing on the internet without asking the obvious question. You do not have their resources. You do have the ten minutes.

Not legal advice. If real money or a real claim is involved, talk to an actual IP lawyer in your jurisdiction.