Great analysis; sounds productizable. Imagine a slack plugin that:
1) detected whenever a link to a podcast episode was shared in a public channel
2) downloaded, 2x'd, and spliced the audio file
3) transcribed the spliced files
4) summarized the transcriptions
5) posted the summary as a reply to the message containing the link
If the user provided their own API key, they could even choose where on the scale from lossy/inexpensive<->lossless/expensive they want their summaries to be.
This would be very cool! I've never built a Slack plugin before but might look into this. In a way, that use case actually fits into the workflow of Slack better than as a standalone site/app, given the looser user expectations about slow (asynchronous) responses there.
For that matter, there is also some very obvious low-hanging fruit I can change on the site too: for example, I'm currently running the various speed transcriptions linearly rather than parallelizing them, so it takes way longer to run than it has to. Updating this is on my to-do list!
Great analysis; sounds productizable. Imagine a slack plugin that:
1) detected whenever a link to a podcast episode was shared in a public channel
2) downloaded, 2x'd, and spliced the audio file
3) transcribed the spliced files
4) summarized the transcriptions
5) posted the summary as a reply to the message containing the link
If the user provided their own API key, they could even choose where on the scale from lossy/inexpensive<->lossless/expensive they want their summaries to be.
Trying out your summarizer now!
This would be very cool! I've never built a Slack plugin before but might look into this. In a way, that use case actually fits into the workflow of Slack better than as a standalone site/app, given the looser user expectations about slow (asynchronous) responses there.
For that matter, there is also some very obvious low-hanging fruit I can change on the site too: for example, I'm currently running the various speed transcriptions linearly rather than parallelizing them, so it takes way longer to run than it has to. Updating this is on my to-do list!