<?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: Paul</title>
    <description>The latest articles on DEV Community by Paul (@tox3d).</description>
    <link>https://dev.to/tox3d</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3751347%2F029e8d9f-4064-4c23-a08e-1ce114327fb2.png</url>
      <title>DEV Community: Paul</title>
      <link>https://dev.to/tox3d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tox3d"/>
    <language>en</language>
    <item>
      <title>From Discord Voice to Meeting Minutes: Local Transcription + Telegram/Slack Delivery</title>
      <dc:creator>Paul</dc:creator>
      <pubDate>Tue, 03 Feb 2026 21:12:27 +0000</pubDate>
      <link>https://dev.to/tox3d/from-discord-voice-to-meeting-minutes-local-transcription-telegramslack-delivery-15dj</link>
      <guid>https://dev.to/tox3d/from-discord-voice-to-meeting-minutes-local-transcription-telegramslack-delivery-15dj</guid>
      <description>&lt;h1&gt;
  
  
  discord2sum — meeting minutes for Discord voice, without the busywork
&lt;/h1&gt;

&lt;p&gt;Discord voice calls are where decisions get made — and also where decisions get lost.&lt;/p&gt;

&lt;p&gt;Someone says “let’s do it this way”, someone else agrees, a couple of tasks are assigned… and then the call ends. A day later you remember &lt;em&gt;that&lt;/em&gt; you agreed on something, but not the exact details, who volunteered for what, or what the next step was.&lt;/p&gt;

&lt;p&gt;That’s the problem &lt;strong&gt;discord2sum&lt;/strong&gt; solves.&lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/toxed/discord2sum" rel="noopener noreferrer"&gt;https://github.com/toxed/discord2sum&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It’s a small Discord bot that quietly turns voice conversations into something you can actually refer to later: a short, structured summary delivered to your chat.&lt;/p&gt;




&lt;h2&gt;
  
  
  What the bot feels like in daily use
&lt;/h2&gt;

&lt;p&gt;You hop into a voice channel with your team.&lt;/p&gt;

&lt;p&gt;When people start talking, the bot joins in the background. It doesn’t interrupt and doesn’t try to be clever in real time. It just listens.&lt;/p&gt;

&lt;p&gt;When the channel becomes empty, you get a message with “minutes”:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;what the call was about (a concise summary)&lt;/li&gt;
&lt;li&gt;what was decided&lt;/li&gt;
&lt;li&gt;what’s next (action items)&lt;/li&gt;
&lt;li&gt;who spoke / who was present (where possible)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You end up with a lightweight paper trail that’s easy to scan, easy to search, and easy to forward.&lt;/p&gt;




&lt;h2&gt;
  
  
  Privacy-first by design
&lt;/h2&gt;

&lt;p&gt;A lot of call‑summary products work by uploading your audio somewhere and letting a cloud service do the transcription.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;discord2sum is built around local processing&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;audio is recorded and processed on your own machine/server&lt;/li&gt;
&lt;li&gt;speech-to-text runs locally (Whisper-based)&lt;/li&gt;
&lt;li&gt;transcripts can be stored locally with retention limits&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For the summary step, you can choose what you’re comfortable with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;use a hosted LLM (OpenAI) for higher-quality summaries, or&lt;/li&gt;
&lt;li&gt;use a local LLM endpoint (e.g. Ollama) for an all‑local pipeline&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Where the summary can go
&lt;/h2&gt;

&lt;p&gt;Telegram is the default because it’s simple and fast.&lt;/p&gt;

&lt;p&gt;But the bot can also deliver the same summary to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Slack&lt;/strong&gt; (via Incoming Webhooks)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;any HTTP webhook&lt;/strong&gt; (as JSON), if you want to push minutes into your own tooling&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That makes it easy to route “call outcomes” into whatever system your team already uses.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why I like this approach
&lt;/h2&gt;

&lt;p&gt;It’s intentionally small and opinionated.&lt;/p&gt;

&lt;p&gt;No calendar integration. No meeting invites. No complex UI.&lt;/p&gt;

&lt;p&gt;Just one job: &lt;strong&gt;when a Discord voice call ends, send a clear summary&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;That’s enough to stop decisions from disappearing — without adding process or forcing people to change how they talk.&lt;/p&gt;

</description>
      <category>discord</category>
      <category>whisper</category>
      <category>opensource</category>
      <category>telegram</category>
    </item>
  </channel>
</rss>
