It's probably insecure, because you don't want to do 75,850,000 sequential evaluations over a network. It would take over a week for a single track with even just 10ms response time.
They run over the network (no, I wasn't trying to cheat, but while stracing to debug my own code, I could see it sending for each query).
Each track is split up into 1000 tests; you can run the separate tests concurrently; which more or less eliminates the latency as the largest test permits 'only' about 400k queries.
Comments
It's probably insecure, because you don't want to do 75,850,000 sequential evaluations over a network. It would take over a week for a single track with even just 10ms response time.
Presumably a secure implementation would just batch up evaluations into groups of ten or a hundred. You could make something like this work.
They run over the network (no, I wasn't trying to cheat, but while stracing to debug my own code, I could see it sending for each query).
Each track is split up into 1000 tests; you can run the separate tests concurrently; which more or less eliminates the latency as the largest test permits 'only' about 400k queries.