Add UI for fuzzy commit threshold

Recap: In the STT there's an algorithm that tries to determine when a
transcript is "stable" enough to commit. If that is too loose, then
accuracy suffers; if too strict, then the audio buffer eventually fills.

To mitigate the problem, I check whether the last N transcripts are
within some edit distance (Levenshtein edit distance) of each other. The
fuzzy matching lets us forgive small instabilities, like differences in
uppercase/lowercase or punctuation, while rejecting large instabilities.

The default value of 8 seems to be in the sweet spot of accuracy &
performance, but it will likely be tuned in the future.

0 files changed, 0 insertions, 0 deletions