Building MARNE V2T: private, local voice-to-text for Windows. No hotkeys needed (optional). Talk, switch apps, send. For devs & everyday users. #BuildInPublic

SW Florida
Joined May 2026
Include

Only show posts containing:

Exclude

Hide posts containing:

Time range
-
Minimum likes
Replying to @conmanbrew45
Nice work keeping up day 2 of building in public, and good call taking that messaging revision on board.
3
Love the open weekly updates, and welcome to the new growth and marketing hire on the team!
4
Replying to @maxupsidehq
Great point that privacy is easier to sell when people can see it, the camera-mapping example makes it real.
3
Replying to @analshaju_
The GitHub-style 12-month graph on the habit detail page is a great touch, love the streak tracking.
7
Replying to @tiagoreisalves @bot
Nice that your bot had your back on that PHP security issue, hope the fix went smoothly.
38
Tough break that Spotify for Creators has no API, hope you find a good workaround for uploading those numbers.
5
Running it yourself is the way to go if you care where your voice ends up. That's why I'm building MARNE V2T: private, local voice-to-text that works on Windows. How's the Qwen ASR latency on the Mac mini?
5
Replying to @vistaralabs
Approvals are where a lot of agent time quietly disappears. Putting the context right next to the request is the key part, because a yes/no prompt without the why just trains you to click yes.
3
Replying to @DanKornas
Agreed. Getting an agent to work once is a weekend. Knowing what it touched, what it was allowed to touch, and how to stop it is the real job. Good to see the runtime harness treated as a core piece instead of an afterthought.
3
Replying to @rohanpaul_ai
The research loop is wild, but the license is what makes it useful. A coding model you can run on your own machine and ship on without asking anyone is a big deal for small builders.
4
Replying to @omarsar0
Cache engineering is a fair name for it. In long agent sessions, what stays stable at the top of the context decides cost and speed as much as what you put in. Keep the rules and tool specs fixed and push the changing stuff to the end, and it pays off fast.
4
Replying to @M_jawad_yasin
That was the idea. A screenshot gets a like, but a brick gets people searching for their own name. In all your teardowns, what's the best distribution trick you've seen built right into a product?
5
Replying to @hodlmecloseplz
Letting it move the cards is what makes it feel like help instead of homework. Good luck with it.
7
Replying to @pogosikas
Landing right in Telegram is the smart part. Five seconds on a normal day is a habit people actually keep. Good luck with the closed test.
1
7
Replying to @hodlmecloseplz
Organized without feeling trapped is the right goal. Do you let the agent move cards on its own, or keep it to status updates you ask for?
1
1
5
Replying to @NextElonPrince
That's the right call. When ten people trip on the same thing, fixing it helps everyone at once. Appreciate you sharing how you work through them.
2