Hacker News Reader

Comment by aznpwnzor | Hacker News Reader

The IOTization of any available media output seems to be the goal of the Chrome team: Chromecast, Chrome Audio, Chromebit. I like it.

View on HN

Coworker sent met this: https://google.github.io/physical-web/

Haven't had the time to check it really out, but seams to be 'iBeacons'.

Google has Beacons called "Eddystone" http://arstechnica.com/gadgets/2015/07/meet-googles-eddyston...

These are called 'urlBeacons' iirc.

Eddystone has a couple different modes. One of them is to transmit a URL, but beacons can also be configured to transmit a UID. Not all Eddystone beacons will be transmitting a URL.

That said, I believe Physical Web does use the Eddystone-URL mode.

Spec: https://github.com/google/eddystone/blob/master/protocol-spe...

It's built on top of Google's beacon format. Every "Physical Web" beacon transmits an Eddystone beacon with a URL.

Definitely check out the video on that page (it's only 5 minutes long). Also, Scott Jenson was interviewed on The Dirt podcast: http://www.freshtilledsoil.com/designing-for-the-future-pt-4...

I have a physical protype of v2 since the IO this year but i have not been able to find anything creative to do with it.

Didn't a teardown of the Chromecast reveal that the device actually ran Android?

It ran Chrome OS

edit:// Wikipedia article seem to state that is was more Android than Chrome OS https://en.wikipedia.org/wiki/Chromecast

Google's marketing department claimed it ran Chrome OS.

However, a group managed to root it and figured out it was "more Android than ChromeOS", derived from Google TV of all things: https://blog.exploitee.rs/2013/chromecast-exploiting-the-new...

Reply on news.ycombinator.com