Click on the leaderboard and prepare to be dismayed. 255 WPM @ 99% accuracy doesn't seem real. A cursory YouTube search shows the best typers maxing out around 210...
Please explain the downvotes. Parent talked about "Chrome Packaged Apps" which are vendor-specific. Instead, I pointed to the cross-browser solution that is recommended by Google and works today.
Right. Bluetooth beacons are a piece of hardware you would have to buy. Basically this tries to accomplish the same thing with just software. Here there is no hardware other than the server (which is provided) and a client computer (which you probably already own).
It really depends on how many routers are in your area. For places in cities, there are tons and tons of routers so its very easy to get pretty good resolution. For places more remote, you might not see many routers and then you would be for more limited in your resolution.
Assuming you wanted to very precisely map a small area (50mx50m or so) to the maximum resolution possible, and you had a budget sufficient to buy and place 20 or so wifi routers, what sort of resolution could you get?
I'm looking at this for gaming applications. Don't need milimeter accuracy but +- 30cm would be good.
The client-side code and the standard are fairly trivial to implement — thanks to Yubico as well — but the problem lies in designing and standardising an extension to the existing mail protocols, and getting that accepted as a common feature for e-mail providers (such as Google and Microsoft) and a common feature in MTAs and MDAs.
I was suprised that when signing in to my Goole account on my Android device with Chrome Beta, the Google Authenticator App pops up to do U2F with my YubiKey NEO via NFC. That was really seamless!
Does anybody know, if it would be possible to use this within a WebView in a native app?
I use the 'Yubico Authenticator' (like Google Authenticator but you have to connect to the Yubikey via NFC for it to reveal your login codes) if I need OATH-TOTP, this has nothing to do with U2F.
However the docs in your second link does indicate that their is some new interoperation between Google Authenticator and U2F. It seams that they use Google Authenticator as a stopgap until browser support the system directly. Pretty strange. This in turn has nothing to do with U2F.
I can not test this stuff very well because I use a Yubikey NEO that is to old for the U2F NFC and a Yubikey 4 that has no NFC. I really hope release a Yubikey 4 with NFC soon.
