My case: how a naive idea became a project nobody else can copy (WorldReacts)

Most solo projects die not from bad execution but from an idea that was, on inspection, a worse copy of something that already exists. Mine nearly did. This is the honest account of how a naive concept became a project with an axis nobody else owns — and the method underneath it, which transfers to any idea you’re holding right now.

The starting point (and the obvious idea)

The observation was simple. When something loud happens in the world — a war, a disaster, a championship final, a premiere, a death — people spend weeks googling the same things: how many casualties, how did it end, who was involved. And the big media give them a chaos of hundreds of stream-articles in which that answer is exactly what’s missing: the breaking-news feed rushes onward, and the event is left unfinished.

So my first idea was the obvious one: make a portal of big events — nice cards instead of news soup.

The first fork: what it must NOT become

It became clear very fast that a “portal of events” slides into one of two things, and both are dead ends for one person:

• Another news site — then I compete with media giants using their own weapon, and lose.
• A static archive-encyclopaedia — then I compete with Wikipedia, and lose.

The key distinction — and the whole project came out of it

News describes what is happening now. Encyclopaedias record what happened, with the feeling stripped out. Neither preserves how the world reacted while it happened.

So the axis became: we record what happened, measure how loudly the world reacted to it, capture what people felt — and keep that as history.

The value isn’t the news itself (everyone supplies that). It’s the world’s reaction to the event, and how that reaction lives over time. Nobody physically has this data today — because nobody collects it systematically at the moment of the event.

How a distinction became a product

From that one difference, the layers assembled themselves on top of a single loud event:

• The event — not a stream of news, only what genuinely makes the world talk.
• The record — a finished, structured brief: what → when it began → how long it lasted → who was involved → the numbers → how it ended. We always write the ending — where media abandon a story halfway, we close it with an outcome.
• The reaction — the human layer: the visitor isn’t an audience, they’re a co-author of the record. Their response becomes part of the event’s history.
• The loudness — a measurement of how noisy the event became, and how that noise rose and faded over time.
• The digest — a derived media product: period summaries that almost assemble themselves from what has accumulated, and go out to a YouTube channel that brings new audience back to the site.

Which closes a loop: a loud event brings traffic → people read and react → the reaction enriches the record → it all accumulates → it becomes a historical layer and a digest → the video brings new people in.

Positioning, in one line

Somewhere between Wikipedia, a news portal and a prediction market — a mix of sociology, statistics, history and news. From Wikipedia: the finished factual record. From news: the relevance and traffic of loud topics. From prediction markets: the idea that collective human attitude is itself valuable data.

The editorial principle as part of the brand

Tragedies are tragedies: a dry, respectful, factual tone, no clickbait, no hype, a source and a date on every number, no side taken in contested conflicts. Celebratory events can be warmer — but just as precise. The tone became part of the identity, not cosmetics on top of it. (This is the same standard as everything I publish: verifiable or it doesn’t ship.)

The decision most people get backwards: foundation vs bonus

The foundation is fresh events from launch onward, and building their social layer over time. Historical events — today’s world reacting to something from the past — are a fun bonus, not the base.

Why: the unique asset only exists after time passes. A year from now I’ll have my own time-series data nobody else has — how loudly an event sounded then, what emotions it produced, how fast interest decayed, how people rated its significance in the moment versus a year later. A competitor launching next year cannot go back and collect that.

The second pillar

The YouTube channel isn’t a marketing appendage — it’s the second leg of the brand: episodes are made straight from the site’s digests, and the channel returns audience to the site. Site and channel promote each other in one identity. (Same logic as my music label case: the audience layer is part of the asset, not an afterthought.)

The result

An idea about “nice event cards” turned into a platform that records not the event, but humanity’s reaction to the event over time. The formula I arrived at:

History = event × the world’s reaction. Everyone records the first factor. Only we record the second.

The log — where it stands

• 2026-08: worldreacts.com is live and early — the structure exists, events are being recorded, the reaction and loudness layers are the point of the build. No revenue, no traffic claims: the data layer becomes valuable only as time passes, which is the entire thesis. Next checkpoints: the first accumulated events with a real reaction history, and the first digest going to video.

Updates get appended here with dates — including if the thesis turns out to be wrong.

What to take from this for your own idea

1. Ask who you compete with, and with what weapon. If it’s incumbents at their own game, stop.
2. Name what each incumbent structurally cannot do — that list is where your angle lives.
3. Look for uncollected data or an unwritten ending, not an unbuilt feature. Features get copied; data collected over time doesn’t.
4. Decide what is foundation and what is bonus — and protect the foundation even when the bonus is more fun to build.
5. Make tone a decision, not an accident. It’s cheap to set early and expensive to change later.

Part of the personal log. Sibling cases: the AI music label, the solo game studio, the self-monitoring project fleet.