From fcf13bae2297a82196140610a2262a36bf5aa7e3 Mon Sep 17 00:00:00 2001 From: tcpsyn Date: Wed, 18 Mar 2026 04:06:12 -0600 Subject: [PATCH] =?UTF-8?q?Fix=20repetitive=20episode=20titles=20=E2=80=94?= =?UTF-8?q?=20require=20specific=20caller/situation=20references?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.6 (1M context) --- publish_episode.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/publish_episode.py b/publish_episode.py index 522f3f6..b7820bf 100755 --- a/publish_episode.py +++ b/publish_episode.py @@ -303,7 +303,7 @@ TRANSCRIPT: {timestamped_text} Generate a JSON response with: -1. "title": A catchy episode title (include "Episode {episode_number}:" prefix) +1. "title": An episode title with "Episode {episode_number}:" prefix. The title MUST reference something SPECIFIC from this episode — a caller's name, their situation, a memorable quote, or a specific moment. Good titles sound like you're telling a friend what happened: "Episode 12: Gary's Goat Problem and the Worst Best Man Speech Ever", "Episode 8: The Lawnmower Feud, a Cursed Wedding Ring, and Darla Finally Calls Back". Bad titles are generic and could apply to any podcast episode: "Secrets and Confessions", "Late Night Tales", "Wild Stories and Hot Takes". Avoid the words: secrets, confessions, tales, chronicles, diaries, unfiltered, raw, real talk. 2. "description": A 2-4 sentence description summarizing the episode's content. Mention callers by name and their topics. End with something engaging. 3. "chapters": An array of chapter objects with "startTime" (in seconds) and "title". Include: - "Intro" at 0 seconds