4 ms·
I've been poking this the last few hours. It uses both audible and inaudible (ultrasonic) frequencies. The URL is passed to a Google service called Copresence t
by moreati 11y ago
I've been poking this the last few hours. It uses both audible and inaudible (ultrasonic) frequencies. The URL is passed to a Google service called Copresence to transform it into a short token - it's this token that's played. The Copresence client, and the playing/listening code are part of Chromium/Chrome 43.x. I think earlier versions won't work with the extension.
Google Tone is similar to http://chirp.io/ http://chirp.io/, which has iOS and Android apps. There are third-party transmitters (but not listeners) which work across browsers. http://piupiu.ga/ http://piupiu.ga/ is the most complete. I wrote a bookmarklet https://moreati.github.io/chirpweb/ https://moreati.github.io/chirpweb/.
- dm2 11y agoIt would be nice if this had an encryption feature, so that it could be used in public and used to send more sensitive information. Do listening browsers require the extension or just that the Dev version of Chrome? Is there any information published about the token?
- moreati 11y agoThis is based on Copresence, which will probably ultimately include something like AirDrop. The audio portion would be used for neighbour discovery, before hand off to e.g. wifi direct. Copresence is already used for the guest play feature of ChromeCast. Listening browsers require the extension. Neither require a Dev release of Chrome - 43.x is the current stable release. Nothing you'd call documentation. Copresence is part of Chromium, so you can dive into the source code if you wish. I'm attempting to reverse engineer the audible portion (just for fun). I'm tweeting as I go https://twitter.com/moreati https://twitter.com/moreati