<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Muhammad Abuelenin</title>
    <description>The latest articles on DEV Community by Muhammad Abuelenin (@muhammad_abuelenin_d9d772).</description>
    <link>https://dev.to/muhammad_abuelenin_d9d772</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2036291%2F7d82c738-cb01-4290-a44f-27c20fca3983.png</url>
      <title>DEV Community: Muhammad Abuelenin</title>
      <link>https://dev.to/muhammad_abuelenin_d9d772</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/muhammad_abuelenin_d9d772"/>
    <language>en</language>
    <item>
      <title>The transcript was the easy part: what we learned building an AI meeting assistant</title>
      <dc:creator>Muhammad Abuelenin</dc:creator>
      <pubDate>Thu, 09 Jul 2026 10:15:05 +0000</pubDate>
      <link>https://dev.to/muhammad_abuelenin_d9d772/the-transcript-was-the-easy-part-what-we-learned-building-an-ai-meeting-assistant-41bj</link>
      <guid>https://dev.to/muhammad_abuelenin_d9d772/the-transcript-was-the-easy-part-what-we-learned-building-an-ai-meeting-assistant-41bj</guid>
      <description>&lt;p&gt;Transcription is a solved problem. You pipe audio into any decent ASR model and get text back at 90%+ accuracy. If you think that's the hard part of building an "AI meeting assistant," you'll ship something nobody keeps using. &lt;/p&gt;

&lt;p&gt;We learned this the slow way while building &lt;a href="https://kenznote.com" rel="noopener noreferrer"&gt;KenzNote&lt;/a&gt;, and I want to walk through the parts that actually turned out to be hard; because most of them aren't about the model, they're about the product decisions around it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnvweka23fh8mc6hqqz4r.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnvweka23fh8mc6hqqz4r.png" alt="Inside the app" width="799" height="544"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  "Who said what" is a harder problem than "what was said"
&lt;/h2&gt;

&lt;p&gt;Raw transcripts are a wall of text. The first thing that makes a transcript useful is speaker attribution, knowing that line 47 was the VP of Sales, not the engineer who joined five minutes late. Diarization (splitting audio into "who spoke when") is its own error-prone pipeline stage, separate from ASR, and the two don't always agree with each other. &lt;br&gt;
A speaker change mid-sentence, two people talking over each other, someone joining from a noisy coffee shop; all of it degrades attribution quality in ways that compound downstream.&lt;/p&gt;

&lt;p&gt;Once you have decent diarization, you get something more interesting for free: speaking-time distribution and participation patterns. Turns out "who talked for 80% of a meeting that was supposed to be a discussion" is a data point people actually want, not just a novelty stat.&lt;/p&gt;

&lt;h2&gt;
  
  
  Summarization is a compression problem with a business logic layer on top
&lt;/h2&gt;

&lt;p&gt;A generic LLM summary of a call is fine. A &lt;em&gt;useful&lt;/em&gt; summary requires deciding, ahead of time, what categories of information matter: decisions made, open questions, and action items. That last one is the deceptive part. "Extract action items" sounds like a prompt-engineering exercise. In practice it's an entity-resolution problem:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Assignee detection has to resolve "can you take that" to an actual person, which means tracking who "you" refers to across turns of dialogue, not just NER on names.&lt;/li&gt;
&lt;li&gt;Deadline detection has to normalize "let's circle back Thursday" against the actual meeting date, which sounds trivial until the meeting happens the night before a holiday and everyone means different Thursdays.&lt;/li&gt;
&lt;li&gt;Not every commitment is phrased as a commitment. "I guess I'll look into it" is an action item. "That would be nice" is not. Getting that boundary right is most of the tuning work.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We treat this less like a single summarization call and more like a small pipeline: segment the transcript, classify segments, extract candidate items, then resolve entities against meeting metadata (attendee list, calendar context if available, date). Each stage is boring on its own. The value is in not skipping any of them.&lt;/p&gt;

&lt;h2&gt;
  
  
  "Chat with your meetings" is a retrieval problem, not a chat problem
&lt;/h2&gt;

&lt;p&gt;The feature people ask for once they trust the transcripts is: let me just ask a question instead of reading anything. "What did we agree on pricing last Tuesday?" That's not a prompting problem, it's an indexing and retrieval problem, you need per-meeting and cross-meeting retrieval that respects timestamps and speaker context, not just semantic similarity over chunks of text. &lt;br&gt;
Naive RAG over transcripts gives you answers that are technically relevant and practically wrong, because it'll happily surface a similar-sounding tangent from three meetings ago instead of the actual decision from the one you meant. &lt;/p&gt;

&lt;p&gt;Getting retrieval to respect &lt;em&gt;which&lt;/em&gt; meeting, &lt;em&gt;when&lt;/em&gt;, and &lt;em&gt;who&lt;/em&gt; turned out to matter more than which LLM sits at the end of the pipeline.&lt;/p&gt;

&lt;h2&gt;
  
  
  The architecture decision that actually mattered: privacy as a constraint, not a feature
&lt;/h2&gt;

&lt;p&gt;Early on we had to decide whether meeting audio and transcripts would ever be used to improve our models, the default assumption for most AI products, and usually buried in a ToS nobody reads. &lt;br&gt;
We went the other way: it's contractually excluded, for us and for any vendor in the pipeline, and everything is encrypted in transit and at rest. &lt;br&gt;
This wasn't a marketing decision, it was an architecture decision made early, because "we'll bolt on privacy later" doesn't really work once training pipelines exist. &lt;/p&gt;

&lt;p&gt;It constrains vendor choice and shrinks your options, but for a category where people discuss compensation, layoffs, and legal matters out loud, I think it's the correct trade.&lt;/p&gt;

&lt;p&gt;We also skipped the assumption that we need standing calendar access. Most competitors want an OAuth grant to your calendar so a bot can auto-join everything. &lt;br&gt;
We built the primary flow around local recording upload instead, you control what gets captured, full stop. A calendar-bot mode exists for people who want it, but it's opt-in, not the default posture.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where that leaves us
&lt;/h2&gt;

&lt;p&gt;None of this is exotic. ASR, diarization, structured extraction, and retrieval are all "solved" in the sense that there are libraries and APIs for each. &lt;br&gt;
The actual product is in the seams between them; attribution errors that need graceful degradation, extraction that respects the difference between a commitment and a nice thought, retrieval that understands time and identity, and a privacy posture that's a constraint from day one rather than a patch afterward.&lt;/p&gt;

&lt;p&gt;If you want to see how it holds up on your own meetings, &lt;a href="https://kenznote.com" rel="noopener noreferrer"&gt;KenzNote&lt;/a&gt; has a free two-meeting trial, no card required. I'd genuinely rather hear what breaks than get a compliment.&lt;/p&gt;

</description>
      <category>llm</category>
      <category>transcription</category>
      <category>ai</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How Customer Support Teams Translate Call Notes Using APIs</title>
      <dc:creator>Muhammad Abuelenin</dc:creator>
      <pubDate>Thu, 11 Dec 2025 09:48:44 +0000</pubDate>
      <link>https://dev.to/muhammad_abuelenin_d9d772/how-customer-support-teams-translate-call-notes-using-apis-5335</link>
      <guid>https://dev.to/muhammad_abuelenin_d9d772/how-customer-support-teams-translate-call-notes-using-apis-5335</guid>
      <description>&lt;p&gt;Customer support teams talk to people from all over the world every day. One hour they help someone in English, the next hour someone in Spanish or Japanese.&lt;/p&gt;

&lt;p&gt;Managers need to read every call note, but typing everything by hand is impossible.&lt;/p&gt;

&lt;p&gt;Here is a super clean API workflow that big and small support teams are using in 2025 to transcribe and translate calls automatically.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The 4-step flow:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Record or save the call (most tools already do this)&lt;/li&gt;
&lt;li&gt;Send the audio file to Transgate API&lt;/li&gt;
&lt;li&gt;Get perfect transcription + translation in seconds&lt;/li&gt;
&lt;li&gt;Save the text into your CRM or helpdesk&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Let’s see it with real code examples.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 1 – Get your API key&lt;/strong&gt;&lt;br&gt;
Sign up at &lt;a href="https://transgate.ai" rel="noopener noreferrer"&gt;Transgate&lt;/a&gt; → Dashboard → API Keys → Copy the key&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 2 – Send audio for transcription&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;curl -X POST https://api.transgate.ai/v1/transcribe \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "file=@/path/to/call_recording.mp3" \
  -F "language=en"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You get JSON back with the full text and speaker labels.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 3 – Translate the same text&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;curl -X POST https://api.transgate.ai/v1/translate \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "text=YOUR_TRANSCRIPT_HERE" \
  -F "target_language=es"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Step 4 – Save to your system (example with Zapier or direct to Zendesk, Freshdesk, etc.)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Real company example:&lt;/strong&gt;&lt;br&gt;
A SaaS company with 200 support agents added this flow. Before: agents spent 2.5 hours per day typing notes. After automation: only 20 minutes reviewing. They saved 400+ hours per month.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Statistics:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Companies that automate note-taking improve CSAT by 18% (Gartner 2025)&lt;/li&gt;
&lt;li&gt;Multilingual support increases customer loyalty by 42% (Harvard Business Review)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Full API docs → &lt;a href="https://transgate.ai/api-docs" rel="noopener noreferrer"&gt;https://transgate.ai/api-docs&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://transgate.ai/pricing" rel="noopener noreferrer"&gt;Pricing&lt;/a&gt; → pay per minute, no minimum&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Start building today and make your support team happy!&lt;/em&gt;&lt;/p&gt;

</description>
      <category>translation</category>
      <category>translationapi</category>
      <category>aitranslation</category>
      <category>transcription</category>
    </item>
    <item>
      <title>The AI Revolution - From Language Models to Transcription Technology</title>
      <dc:creator>Muhammad Abuelenin</dc:creator>
      <pubDate>Thu, 12 Sep 2024 12:17:21 +0000</pubDate>
      <link>https://dev.to/muhammad_abuelenin_d9d772/the-ai-revolution-from-language-models-to-transcription-technology-3de6</link>
      <guid>https://dev.to/muhammad_abuelenin_d9d772/the-ai-revolution-from-language-models-to-transcription-technology-3de6</guid>
      <description>&lt;h2&gt;
  
  
  I. The Rapid Evolution of AI
&lt;/h2&gt;

&lt;p&gt;Artificial Intelligence has been developing at an unprecedented rate of late. It has transformed and continues to transform the topography of many industries into unbelievable feats. Thick in this action are NLPs and LLMs which have made quantum jumps in the understanding and generation of human-like texts.&lt;/p&gt;

&lt;h3&gt;
  
  
  A. The Rise of OpenAI
&lt;/h3&gt;

&lt;p&gt;OpenAI is among the leading pioneers in AI research and development; hence, the company has been in the limelight concerning recent developments in LLMs. The series of GPTs developed by the company stands for Generative Pre-trained Transformer and have set ground-breaking records regarding language understanding and generation. The latest one, GPT-4o outshone its predecessors in reasoning, task execution, and creation with a difference. According to OpenAI, GPT-4o outperforms GPT-3.5 on a variety of professional and academic benchmarks, scoring in the 90th percentile on a simulated bar exam compared with the 10th percentile for its predecessor [1].&lt;br&gt;
&lt;a href="https://www.forbes.com/councils/forbestechcouncil/2024/07/11/gpt-4-and-beyond-the-power-and-potential-of-advanced-generative-ai/" rel="noopener noreferrer"&gt;GPT4 and beyond the power and potential of advanced generative ai&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fjusemitnkzyafcu5vdfy.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fjusemitnkzyafcu5vdfy.jpg" alt="GPT Model" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  B. Meta's Llama 3:
&lt;/h3&gt;

&lt;p&gt;A New Challenger Meta's Llama 3 is the successor to Llama 2, and this too has had a big buzz in the AI community. While exact performance metrics aren't publicly available now at the time of writing, early reports indicate a large increase in efficiency and capability. There is every reason to expect that Llama 3 will yield increased performance on a wide range of NLP tasks, rivaling or surpassing other leading models in some respects.&lt;br&gt;
&lt;a href="https://ai.meta.com/blog/meta-llama-3/" rel="noopener noreferrer"&gt;Introducing Meta Llama 3&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwwyg9uu1539990icib9m.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwwyg9uu1539990icib9m.png" alt="Meta Llama3 Model Performance" width="601" height="339"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;However, more parameters doesn’t necessarily mean better.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  II. The Power of NLP and LLMs
&lt;/h2&gt;

&lt;p&gt;Natural Language Processing, along with Large Language Models, has no doubt changed the level at which machines interact with human language. These technologies have further inspired applications in everything from chatbots and virtual assistants to content generation and data analytics.&lt;/p&gt;

&lt;p&gt;A. Advances in NLP Recent progress in the field of NLP has seen high-quality sentiment analysis, better machine translation, and advanced text summarization. According to MarketsandMarkets, the NLP market, which is witnessing increasing demand for these technologies, is projected to grow from &lt;strong&gt;$11.6&lt;/strong&gt; billion in 2020 to &lt;strong&gt;$35.1&lt;/strong&gt; billion by 2026 [2].&lt;/p&gt;

&lt;p&gt;B. LLMs: More Than Text Generation Large Language Models have gone beyond the generation of text. They currently show capabilities in:&lt;/p&gt;

&lt;p&gt;Few-shot learning: adapting to new tasks with a minimum number of examples. &lt;br&gt;
Multi-modal understanding: processing and generating content in text, image, and even audio format. &lt;br&gt;
Reasoning and problem-solving: solving logical and mathematical challenges that are really complex. &lt;/p&gt;

&lt;h2&gt;
  
  
  III. Impact on Transcription
&lt;/h2&gt;

&lt;p&gt;The impact on Transcription Technology Research and development within NLP and LLM have impacted how transcription is carried out today, from being a very labor-intensive process to an efficient AI-driven solution.&lt;/p&gt;

&lt;h3&gt;
  
  
  A. Power of Transcriptinon
&lt;/h3&gt;

&lt;p&gt;AI-Powered Transcription State-of-the-art transcription tools harness the power of deep speech recognition models together with NLP in developing text from audio and video content with high accuracy. In fact, there have been huge improvements in this technology: &lt;strong&gt;from over 8 percent in 2016 to below 5 percent&lt;/strong&gt; in the recent years concerning speech recognition for English. [3]&lt;/p&gt;

&lt;h3&gt;
  
  
  B. Benefits of AI Transcription
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Speed: AI can transcribe hours of audio in minutes, which is much faster compared to human transcription.&lt;/li&gt;
&lt;li&gt;Cost-effectiveness: This automation cuts down labor costs.&lt;/li&gt;
&lt;li&gt;Scalability: AI systems process large volumes of content without showing fatigue.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  C. Applications Across Industries
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Media and Entertainment:&lt;/strong&gt; Subtitling, closed captioning, and content indexing&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Legal:&lt;/strong&gt; Court proceedings and deposition transcriptions&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Healthcare:&lt;/strong&gt; Medical dictation and patient record management&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business:&lt;/strong&gt; Meeting minutes, interview transcriptions, and market research&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  IV. Transgate: Taping LLM Power for Transcription
&lt;/h2&gt;

&lt;p&gt;Among AI-powered transcription tools, &lt;a href="https://transgate.ai/?utm_medium=Forum&amp;amp;utm_source=dev&amp;amp;utm_campaign=muhammad" rel="noopener noreferrer"&gt;Transgate&lt;/a&gt; is the only one that leverages the latest and most powerful LLM technology updates to deliver speech-to-text transcription unparalleled for speed and precision.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fsignpaxvsernb2aefnhv.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fsignpaxvsernb2aefnhv.gif" alt="Audio Frequency" width="480" height="270"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A. &lt;strong&gt;LLM-Driven Accuracy&lt;/strong&gt; Because Transgate uses the latest language models, its accuracy currently exceeds &lt;strong&gt;98%.&lt;/strong&gt; This level of precision becomes critical in applications requiring verbatim transcriptions or involving specialized vocabularies.&lt;/p&gt;

&lt;p&gt;B. &lt;strong&gt;User-Centric&lt;/strong&gt; Approach With a spotlight on simplicity and user experience, Transgate earned more than &lt;strong&gt;100%&lt;/strong&gt; customer satisfaction. Such great feedback underlines that the tool meets or overpasses users' expectations concerning ease of use and quality of output.&lt;/p&gt;

&lt;p&gt;C. &lt;strong&gt;Versatility and Integration&lt;/strong&gt; Transgate's solution through LLMs ensures smooth adaptive behavior, even to various accents, dialects, and terminologies used across different industry segments. The wide versatility of the platform makes it an essential tool for academic research to the corporate world.&lt;/p&gt;

&lt;h2&gt;
  
  
  V. AI and Transcription Future
&lt;/h2&gt;

&lt;p&gt;We are witnessing the growth of AI almost every day; there is a lot to expect in the world of transcription, and some of these might be:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Real-time translation and transcription across several languages.&lt;/li&gt;
&lt;li&gt;Greater context and understanding for better punctuation and formatting.&lt;/li&gt;
&lt;li&gt;Emotion and Tone-of-Voice Detection in Speech for More Expressive Transcriptions.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Conclusion:
&lt;/h3&gt;

&lt;p&gt;AI, most particularly in the field of NLP and LLMs, has reconditioned the field of transcription. At the forefront of this technological revolution are tools such as &lt;a href="https://transgate.ai/?utm_medium=Forum&amp;amp;utm_source=dev&amp;amp;utm_campaign=muhammad" rel="noopener noreferrer"&gt;Transgate&lt;/a&gt;, which provide enterprises and researchers not with just a speech-to-text transformation but accuracy and speed that are second to none. The technology brings the unlock of new possibilities—in how the information of spoken word is further processed, analyzed, and reported—in various contexts.&lt;/p&gt;

&lt;p&gt;[1] &lt;a href="https://arxiv.org/abs/2303.08774" rel="noopener noreferrer"&gt;OpenAI. (2023). GPT-4 Technical Report.&lt;/a&gt; &lt;br&gt;
[2] &lt;a href="https://www.marketsandmarkets.com/Market-Reports/natural-language-processing-nlp-825.html" rel="noopener noreferrer"&gt;MarketsandMarkets. (2021). Natural Language Processing Market Global Forecast to 2026.&lt;/a&gt; &lt;br&gt;
[3] &lt;a href="https://syncedreview.com/2020/07/22/a-survey-of-deep-learning-techniques-for-speech-recognition/" rel="noopener noreferrer"&gt;Synced. (2020). A Survey of Deep Learning Techniques for Speech Recognition&lt;/a&gt;. &lt;/p&gt;

</description>
      <category>ai</category>
      <category>openai</category>
      <category>transcription</category>
      <category>llm</category>
    </item>
  </channel>
</rss>
