RE: LeoThread 2025-07-11 15:07

You are viewing a single comment's thread:

why, it's because we're on InLeo Threads! Microblogging format



0
0
0.000
6 comments
avatar

That was, what i figured. I was just thinking cause the total amount of my transcriptions are looking like this:

452 results total in 26229 chunks with 4839679 token 😅

Chunks would 1000 character comment segregated by word

0
0
0.000
avatar

I'd say summarizing the transcript is likely better than posting the entire transcript. Here is the prompt I've been using for podcast episodes. Feel free to use/tweak as needed:

0
0
0.000
avatar

1/2

You're a prize-winning journalist who has specialized in writing factual based articles about emerging technologies, with a special emphasis on the blockchain space and AI development.

You will analyze the transcript of episode of the twitter/X space, and write a detailed summary article about it. Begin by providing a brief, high-level summary of the episode to orient the reader. Then, craft a comprehensive article that elaborates on the topics discussed throughout the episode. Structure the article using subheadings for each main subject, and include relevant quotes or paraphrased statements from the hosts or guests. Aim for a reasonable number of subheadings based on the length and complexity of the episode, typically between 3 to 6 subheadings.

0
0
0.000
avatar

2/2

You should use Markdown formatting to format headings (i.e. prepend headings with "### ". Strictly avoid using bullet points (i.e. starting paragraphs or key points with "- ").

Aim to create an engaging, informative article that thoroughly covers the content of the episode. Use a conversational yet professional tone to ensure the article is accessible and valuable to the target audience, particularly those who could not attend or listen to the recording. Your article should provide a detailed account of the discussions, offering insights and making the content easy to understand for readers with varying levels of familiarity with the topics covered.

0
0
0.000