Service enabling users to subscribe to podcasts and receive episode transcripts by email.
Landing Page
Example Transcript Email
I developed this shortly after OpenAI's Whisper was released with the idea of launching it as a product, but decided not to move forward with that for various reasons and am open-sourcing it instead.
All of the core functionality is working, so hopefully it can be useful to somebody!
The frontend is a relatively simple NextJS app that allows users to sign up and manage their podcast subscriptions.
The backend is split between transacription and "management" (ie. everything else: polling/downloading for new episodes, detecting new transcripts, sending emails, etc.). This allows management to be run in a generic environment while transcription can be done on separate hosts with eg. GPU hardware (eg. I ran management on a Raspberry Pi and transcription on a laptop with a GPU). While I haven't tested it, scaling to multiple transcription instances should be relatively straightforward.
- app - NextJS Frontend
- backend - Code for monitoring for new episodes, running the transcription pipeline, and uploading the results.
- supabase - DB schema, triggers, functions, and scripts
Account verification triggers the creation of:
- account token
- podcast (if doesn't exist)
- subscription
The flow is as follows:
Verification link clicked ->
email_confirmed_at on auth.users updated -> triggers user_verified() function
- creates token
- creates podcast if not exists -> triggers
new_podcast()- sends notify on
new_podcastchannel
- sends notify on
- creates subscription
When a new podcast is inserted into the podcasts table it sends a notify on new_podcast
The ./supabase/db/feeds.py script listens to this, starting the feed update process which will populated the podcast record with all the data and insert the most recent episode.
When a new episode is inserted into the episodes table it triggers new_episode() which updates all subscriptions for that podcast with pending_publish_id = NULL, setting pending_publish_id to the newly inserted episode ID.
It also notifies on new_episode which kicks off transcription generation.
When a new transcript is complete, the email html is uploaded to R2 and the object ID is set on the episode filename column. This update triggers the new_transcript() function which notifies on new_transcript. The mailer script listens to new_transcript and processes subscription publishing for the new transcript.