Orange Cheeto Browser extension that replaces Trump with nicknames

Name: Orange Cheeto Browser extension that replaces Trump with nicknames
Availability: InStock
Author: philco

by philco·Feb 17, 2026·4 points·0 comments

Visit Project View on HN

AI Analysis

●●SolidCozyNiche Gem

TreeWalker + MutationObserver text-swap with case preservation; solid engineering on a novelty premise.

Strengths

•Technical architecture is genuinely reusable: TreeWalker skips scripts/inputs/iframes; Fisher-Yates shuffle bag prevents nickname repetition; case preservation via regex is non-obvious.
•Zero dependencies, plain JS, Manifest V3 compliant, local-only (no tracking, no exfil); privacy-first engineering is credible.
•Multi-browser support (Chrome, Firefox, Safari); simple settings sync via Storage API; animation polish with prefers-reduced-motion respect.

Weaknesses

•Core premise is a novelty—joke extension that replaces one word. Usefulness decays after first few hours of humor.
•No evidence of staying power: architecture is reusable, but the extension itself is single-purpose and bound to one person/phrase.

Post Description

I built a browser extension that does text replacement across all websites -- specifically replacing "Trump" with rotating humorous nicknames.

The interesting technical bits:

- TreeWalker for DOM traversal (skips scripts, inputs, contenteditable, iframes)

- MutationObserver with debouncing for SPAs and dynamically loaded content

- Fisher-Yates shuffle bag for even nickname distribution (no repeats until all are used)

- Case preservation via regex (TRUMP -> MANGO MUSSOLINI, Trump -> Mango Mussolini)

- CSS-only animations with prefers-reduced-motion support

- Zero dependencies, plain JS, Manifest V3

The architecture is generic enough to fork for any text replacement use case. All the replacement logic lives in a single file.

No external requests, no analytics, no data leaves the browser. Settings sync via Chrome Storage / browser.storage.

Available for Chrome, Firefox, and Safari. Free.

Feedback on the implementation welcome -- the code is straightforward and I'd rather someone tell me my MutationObserver setup is wrong than find out the hard way.