~/gatekeypairs · about · privacy · terms

▮about

about this channel and the person making it.

I've been writing backend code for over a decade. I use cryptography every day — signed commits, SSH into prod, mTLS between services, PGP for the one team chat that still insists on it — and for years I ran on vibes. The tools mostly worked. I mostly didn't have to know.

Then at some point in the middle of a 2 AM cert-rotation, I realized I couldn't explain why our root CA was self-signed and that was fine, but a self-signed leaf cert wasn't. I went looking for a clean, 30-second answer and found either RFCs or marketing pages. Nothing in between.

gatekeypairs is that in-between. One claim per clip. The thing a senior engineer would tell you while waiting for a deploy to finish.

Every clip follows the same shape:

# clip recipe
def clip():
    hook   = "one surprising claim"
    body   = "the mechanism that makes it true"
    payoff = "why you, the working dev, care"
    return 25 <= len(spoken) <= 35  # seconds

Scripts are drafted with help from Claude (Anthropic), narrated with Inworld TTS, captioned via Whisper, b-roll pulled from Pexels. The technical content is human-reviewed before publish — if something's wrong in a clip, it's wrong because I missed it, not because a model invented it.

The publish toolchain is open-source-ish, in the sense that I built it for this and might write it up later. Nothing about the technical claims depends on which tools render the clip.

Cryptography is one of those domains where being approximately right is being wrong. If you see a claim in a clip that's incorrect, misleading, or missing context that changes the conclusion, write to team@gatekeypairs.com. I'll either fix the script and re-post or pin a correction on the clip.

Corrections are public-by-default unless you ask otherwise. That feels like the right norm for a technical channel.

This channel isn't affiliated with any company, vendor, certificate authority, or standards body. No sponsorships. No referral links. If a clip names a tool, it's because the tool is the cleanest example, not because anyone paid for the placement.