Internet protocol stories.
The obscure technical decisions behind email, the web, and messaging that shaped how billions of people communicate. Niche but loyal, tech-curious audience, evergreen.
What works in this niche
- Explaining a protocol in terms of the human problem it solved rather than the technical spec
- Flow diagrams that make an abstract standard visible and followable
- The contestation or alternative that was defeated, held as the third-act turn
- Connecting a protocol decision to something the viewer touches in their daily life
- A clear separation between how the protocol was supposed to work and how it does
Format: 9 to 14 minute explainers over spec documents, flow diagrams, and B-roll. Documentary voice, problem-design-consequence structure, re-hook at 90 seconds.
Hook patterns that earn clicks
- Question hook: the invisible standard every email relies on, from a committee meeting in the 1980s
- Contrarian: the protocol everyone uses was not the best design, it was the one that shipped
- Data shock: the number of requests per second that flow through this standard right now
Sub-niches to mine
Narrower angles inside this niche with room to own a lane.
- Email protocols and the spam arms race they enabled
- Web standards decided by a single committee vote
- Messaging protocols that competed before one consolidated
- Security protocols and the vulnerabilities that exposed them
- The DNS system and the fights over who controls it
- Protocols deliberately broken or deprecated and what replaced them
Top performers we track
Anonymized to protect operators. Revenue figures are estimates from public engagement, not declared earnings.
Common pitfalls
- Leading with the RFC number or acronym rather than the human problem
- Technical depth that loses a general audience in the first two minutes
- Flow diagrams that are technically accurate but visually unclear
- Ignoring the political and organizational battles behind standardization
FAQ
Who is the audience for protocol history?
Tech-curious viewers who want to understand why the internet works the way it does, not just that it works. The audience is smaller than pop-culture niches but loyal and shares deep cuts obsessively.
How do I keep it from becoming a lecture?
Lead with the problem that existed before the protocol and the compromise that was made to ship it. The spec is the answer to a question; start with the question.
Why the mid-to-upper RPM?
Tech and infrastructure topics attract solid advertiser bids. We keep the range conservative while new channels calibrate lower at first.
Want the full pipeline tuned for internet protocol stories?
Script, five A/B titles, SEO description, and thumbnail. Tuned per channel archetype. From operators with 1B+ views.