Pretty sure I just broke the Wispr Flow state machine. I am now in word debt for the next several lifetimes.
So I was on a massive, non-stop 20-minute continuous dictation session explaining a technical trade breakdown to a buddy while Flow was running in the background. It captured the audio flawlessly, but when it processed the payload... the backend completely lost its mind.
Check out that absolute unit of a negative number: -6,241,717,869,601,868,892 words remaining.
As a builder myself, this looks like a classic int64 underflow/casting glitch where the quota - used state machine rolled straight over into the negative quintillions. Even the frontend localization comma formatting is choking hard trying to parse it.
According to the UI, "Flow will slow down until next week" but given that I’m currently billions of words in debt, I think my basic tier is bricked until the death of the universe
Hey dev team, I think I found your ultimate edge case. Do I win a few months of a Pro subscription for breaking the simulation, or do I need to start paying off my word debt in installments? 😂
(Shoutout to the transcription engine though, it actually grabbed everything before the backend exploded!)