Hi, I built the client UI for this and... yea, I really wanted to get Firefox working :(
We needed a way to measure voice-to-voice latency from the end-user's perspective, and found Silero voice activity detection (https://github.com/snakers4/silero-vad) to be the most reliable at detecting when the user has stopped speaking, so we can start the timer (and stop it again when audio is received from the bot.)
Silero runs via onnx-runtime (with wasm). Whilst it sort-of-kinda works in Firefox, the VAD seems to misfire more than it should, causing the latency numbers to be somewhat absurd. I really want to get it working though! I'm still trying.
Do you know why there's a difference in the performance of the algorithm in another browser? I would expect that all browsers run the code exactly the same way.
But that's basically complaining that firefox doesn't just blindly adopt whatever google proposes. A lot of the concerns are about security and privacy, the thing that mozilla is praised for doing better than google.
And no, you're not forced to use google. You can make native applications when it's necessary to use privileged interfaces.
You prefer the management of Chromium, which makes billions a year from invading your privacy and force feeding you advertising, while also ruining the internet ecosystem?
Thanks for sharing. I did make some changes that seems to have improved things, although I do still see the occasional misfire. Perhaps good enough to remove that ugly red banner though!