Would you trust a meeting recorder more if you could read its code?
by•
I build a Mac meeting recorder, and the whole pitch rests on one claim: your audio and its transcription never leave your machine.
The problem is that this is exactly the sort of thing everyone says. You cannot check it from a privacy policy.
So I published the source. The capture engine and the on-device transcription pipeline are readable, under GPL.
Honest question for this crowd: does that actually change anything for you? Or is source code the thing we all say we want and never open?
26 views
Replies
@umberto_abbatantuono Thanks! I use Corder myself every day, and I am simply sharing my own solution here. It is free and private, and it solves exactly the problems I had
If people like it, a Windows version will follow very soon, as soon as I have a way to test on Windows
I have been using Corder for about two months, back from when it was still pretty rough, so treat this as a biased comment from an early tester.
To actually answer your question: the code being open changed nothing for me at first, because I was never going to sit down and read it. What it changed was the feeling when I did go and look. It matters less as something I read and more as something I could read on the day I stop trusting you.
The other thing worth saying is that bugs get fixed fast here. I have reported some genuinely annoying things and they were usually gone within a day or two, which is not what I expected from a one-person project.
It is not perfect. The mic still picks up my keyboard when I am not wearing headphones. But I use it for real calls now, and that is the only endorsement that means anything.