Is your password at risk from the noises you make typing it? Betteridge's law applies, for now.
"I am trying to gather more data in order to better understand the limitations of the approach. Anyone willing to help with that can use the “Save” button on the page after recording a sample and send it to me so I can analyze it. I don’t have access to the recordings that people are doing because the test runs completely in the client browser and in order to keep their privacy none of the data is stored or uploaded back to me.
"Another thing you can try is to wait for the analysis to for a little longer. In some cases, it takes a bit more iterations for the algorithm to start showing meaningful results. Also, you can try recording more text - for example, 200 characters. Use the slider before pressing the Init button." "The main factor that determines if Keytap will succeed or not, is how accurately it can match the key sounds to one another . Currently, Keytap uses a time-domain cross-correlation metric to match the keys with one another and it is definitely not perfect. It was actually a surprise to me that it performs that well. If this part of the algorithm is improved somehow, I believe it can become highly efficient.
"The typing speed factor on the other hand I think is not very important. In the Keytap3 test, I have suggested a certain speed limit simply because it makes automation much easier. However, a bad actor could easily analyze the recording and manually select the key sounds with high accuracy, instead of relying on automation to do that.