I guess that leaves electron and tauri?
Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts
41–50 of 55 posts
Re: Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts
#42Pardon my ignorance, but is recording a call without informing the other participants considered bad practice? Congrats on the launch! :tada:
Re: Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts
#4370 cents per hour is a mountain of fees... basically a $1 per meeting. Sheesh.
Re: Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts
#44Most transcript system we have tried bundle everything that is said by the onsite people as a single entity which pretty much destroys the value of the transcript; especially if people in that room disagree with each other; reading the transcript makes it feel that the onsite guys is very schizophrenic
Re: Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts
#45Checks out the website[1]:
> By default, all media associated with a recording is retained indefinitely. If needed, you can request early deletion of this data at any time via our API.
Data shared with 25 "subprocessors", some of who also retain data indefinitely. Yikes!
Re: Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts
#46> we support 0-day retention, and we don’t train models on customer data. Checks out the website[1]: > By default, all media associated with a recording is retained indefinitely. If needed, you can request early deletion of this data at any time via our API. Data shared with 25 "subprocessors", some of who also retain data indefinitely. Yikes! [1]: https://security.recall.ai/
Re: Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts
#47> we support 0-day retention, and we don’t train models on customer data. Checks out the website[1]: > By default, all media associated with a recording is retained indefinitely. If needed, you can request early deletion of this data at any time via our API. Data shared with 25 "subprocessors", some of who also retain data indefinitely. Yikes! [1]: https://security.recall.ai/
There's no contradiction. One statement is about the default, the other is about the possibility.
[1]: https://arstechnica.com/tech-policy/2025/06/openai-confronts...
Re: Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts
#4870 cents per hour is a mountain of fees... basically a $1 per meeting. Sheesh.
It is a lot but processing real time video and audio streams inherently consumes alot of CPU. So they may not be making as much profit on that price as you'd think. I run an open source alternative to Recall (for meeting bots), and our costs are about 8 cents per hour.