How I do the reading.

fetch is the distance wind travels over open water before it becomes a wave. Nothing becomes a wave immediately — a wave isn't made by force, it's made by a long, uninterrupted run of small pressure over distance. The variable is distance, not effort.

You never see the fetch. You only ever see the wave.

The method

I kept running into questions that needed real research to answer, and never finding the time to read the papers properly. So this is how I do the reading. Two hosts take one question at a time and argue it out: what the research found, what it doesn't support, and what everyone is about to claim it says.

Hana has done the thing. Gus has read the research. Neither is a foil — an episode that always resolves in the same host's favour has stopped being a conversation and become a lecture with a sidekick. They disagree properly, and I remember far more from listening to them fight than from reading it on my own.

The hosts are synthetic

Hana and Gus are synthetic voices. That isn't a disclosure, it's the method: I built two people to argue so the material would stick.

Two forms, one page

Every episode ships as audio and as a written piece. The written version isn't a transcript — it's the same material rebuilt for reading: tighter, headed, scannable, with the sources linked where the claim is made. Both live on the same page, so you can listen to the argument or read the shorter version.

The caveat is the interesting part

Most shows bury the limitation in the last thirty seconds. Here it's the turn. Where a study doesn't support the headline it's been given, the episode says so — including when that costs the episode its best line. Every claim attributed to a named source gets checked against that source.

There's no schedule

Episodes get made when something worth making surfaces, not on a timer. The gap between two of them might be a day or a month. An empty queue is an acceptable outcome; a filler episode isn't.

Get in touch

hello@longfetch.nz — made in New Zealand.