> I saw this tweet: "Hear me out: X but it's only voice messages (with AI transcriptions)" - and couldn't stop thinking about it.

> Why this exists: AI-generated content is drowning social media.

> Real-time transcription

... So you want to filter out AI content by requiring users to produce audio (not really any harder for AI than text), and you add AI content afterward (the transcriptions) anyway?

I really think you should think this through more.

The "authenticity" problem is fundamentally about how users discover each other. You get flooded with AI slop because the algorithm is pushing it in front of you. And that algorithm is easily gamed, and all the existing competitors are financially incentivized to implement such an algorithm and not care about the slop.

Also, I looked at the page source and it gives a strong impression that you are using AI to code the project and also that your client fundamentally works by querying an LLM on the server. It really doesn't convey the attitude supposedly motivating the project.

Nice tech demo though, I guess.

Curious what made you think the backend uses LLMs for content generation?

To clarify:

1. transcription is local VOSK speech-to-text via WebSocket

2. live transcript post-processing has optional Gemini Flash-lite turned on which tries to fix obvious transcription mistakes, nothing else. The real fix here is more accurate transcriber.

3. backend: TypeGraphQL + MongoDB + Redis

The anti-AI stance isn't "zero AI anywhere", it's about requiring human input.

AI-generated audio is either too bad or too perfect. Real recorded voice has human imperfections.