What My Guests Were Actually Seeing

A guest wrote to me last week about the page PodGlue builds for them after we record. Nice note, but there was a line in the middle of it I couldn't let go: the quotes section was empty.

I opened their page. Empty. I opened a few more. Also empty.

Then I opened one from an episode I'd walked through by hand, and the quotes were right there. Which told me the problem wasn't the transcript, or the guest, or anything about that particular conversation. It was that some episodes go through PodGlue automatically, on a schedule, without me touching them, and those were the empty ones.

Two different problems wearing the same coat

The automated path was pulling quotes out of the conversation and then never putting them anywhere the portal knew to look. The page asked for quotes, found nothing where it expected them, and did the polite thing: it showed an empty section instead of an error. So nothing ever looked broken. It just looked like your episode didn't have any good lines in it.

That's the part that bothered me most. A guest reads an empty quotes section as a verdict on the conversation.

The second problem was on the episodes that did have quotes. PodGlue was pulling the best lines from the recording, but it wasn't checking who said them. So a guest would land on their page and find my sentences sitting there under a heading that was supposed to be about them.

And while I was in there, I found a third thing I wasn't looking for. Some of the share copy PodGlue writes for automated episodes had a link in it that was never finished, the raw placeholder, sitting in the text, ready to be sent to a guest. Others pointed at the private side of the app, which a guest can't open at all.

What changed

Quotes are now filtered to the guest before anything else happens, and the cap is applied after that filter instead of before it. That sounds like a small ordering detail. It isn't, the old order meant an episode where I talked a lot could fill the whole quota with my own lines and leave the guest with almost nothing.

If the guest-only set comes back thin, PodGlue quietly runs a second pass that was built for exactly this and merges what it finds, skipping anything it already has. If that second pass fails, you still get the first set. It never costs you the quotes you already had.

Automated episodes now do the same derivation the manual path always did, so the portal finds what it's looking for.

And every link in generated share copy now resolves to the real public episode page, or doesn't get written at all. There's one place in the code that decides what a public episode link looks like, per side of the app, and it checks whether the episode is genuinely public before handing one out. No placeholder text can reach a guest.

The uncomfortable part

None of this threw an error. Nothing turned red. The pages loaded, the sections rendered, the copy was grammatical. Every automated check I have said things were fine, because from the inside they were fine, the code did exactly what it was told.

It took a guest mentioning it in passing to find any of it. I've been thinking about that all week: the failures worth worrying about aren't the loud ones. They're the ones that look like a normal, slightly disappointing day.

I'm going back through the rest of the guest portal now with one question, which is not "does this work" but "what does this look like to someone who has never seen it before and won't tell me if it's wrong."

If you've had a guest go quiet after you sent them their page, it might be worth opening it yourself. That's the whole reason PodGlue makes the page in the first place, the episode is the byproduct, the relationship is the thing, and a page that quietly says nothing quotable happened here is doing the opposite of its job.