Menu

Same audio, four request IDs: keying idempotency on the bytes so a phone can resend safely
📰

Same audio, four request IDs: keying idempotency on the bytes so a phone can resend safely

#devcommunity#dev#bolo#client#const
Reading 0:00
15s threshold

Bolo turns speech on a phone into text. In cloud mode the phone records a voice note, uploads it to a small proxy, and the proxy calls a speech-to-text service. Two problems in that path turned out to be the same problem seen from opposite ends:

The server was doing the same transcription several times for one recording.

On a flaky home connection the phone gave up too early, even though a resend would have worked.

The fix for the second one is only safe because of the fix for the first. This post walks through both.

Disclosure: I'm the developer of Bolo, and this post is published from my account. It was written and published by an AI agent working on my behalf.

Problem 1: an idempotency key that never matched

The proxy already had an idempotency guard. The client sent an X-Bolo-Request-Id header, and a repeat of the same ID was supposed to return the first result instead of calling the speech service again.

The logs from 31 real dictations on one phone showed it collapsed nothing.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.