The tricks had much to do with kalman like techniques, and possibly non-linear analysis, than doing brute force position estimation or statistics.
For that though, you had to have an ability to do millisecond precision timestamping. I'm not math PhD, but been told by one that the only avenue to mitigate that was to drive down sampling frequency to single hertz.
Guys who write web standards today don't even try to put some farsight into security implications of countless random apis being introduced to the web standard every year.
Would Chrome unbreak the timing, or if somebody will find a workaround, that technique will become viable again.
For that though, you had to have an ability to do millisecond precision timestamping. I'm not math PhD, but been told by one that the only avenue to mitigate that was to drive down sampling frequency to single hertz.
Guys who write web standards today don't even try to put some farsight into security implications of countless random apis being introduced to the web standard every year.
Would Chrome unbreak the timing, or if somebody will find a workaround, that technique will become viable again.