Repository navigation
Save count of tries #13
Description
Activity
Do you mean it should be used to lower the score? If yes, I'm not sure this will be very understandable from a user point of view. I mean, there are many reasons to restart a test (typo, have to switch tab, etc.), and it could finally penalize legit restarts. Users would still have ability to remove local storage anyway, so it will double penalize non-advertized users. What do you think?
For the metrics display during the test, I think we can totally display live information while a race is in progress (correction counts, etc.). Is that the initial lack?
No not to lower it (I would be fucked), simply as a metric we could show, or could be used for cheat-detection too. This is different from the live information, it's only the count of times you started a test without finishing it
Oh ok, understood. Yep, can be good as cheat detection, I mean, a 100% perfect score with 75WPM on the first try is inhuman (unless on Ruby, btw).
Since we don't have any metric at all until the user finishes the race, it would be cool to save in localStorage or similar the count of attempts for each test and send that upon race completion.