4 ms·

I kinda hoped the devices would actually serve the apps themselves. I guess a URL makes more sense though. But I wonder if it will lead to physical devices that

I kinda hoped the devices would actually serve the apps themselves. I guess a URL makes more sense though. But I wonder if it will lead to physical devices that give 404s when they are obsoleted. Anyway, this seems pretty exciting.

garethadams 12y ago
There's no reason it couldn't mean that anyway - if a device is open to the Internet then the URL it serves via Physical Web could easily be its own. But it allows for less-smart devices too. The biggest problem I can see, as with all proximity devices, is spoofing. How do I know the item listed as "Bus Stop" is actually the bus stop, and not someone's malicious Raspberry Pi hidden in the bush next to it?
- tetrep 12y ago
  >How do I know the item listed as "Bus Stop" is actually the bus stop, and not someone's malicious Raspberry Pi hidden in the bush next to it? The same way you know that top search results are accurate for a given word/phrase. As stated multiple times throughout the introduction[1] the solution for filtering out spam will probably have an implementation similar to internet search engines. [1]: https://github.com/google/physical-web/blob/master/documentation/introduction.md https://github.com/google/physical-web/blob/master/documenta...
  - donutz 12y ago
    How do I know the top 100 items listed as "Bus Stop" aren't someone's malicious raspberry pi hidden in the bushes, spitting out hundreds of URLs and varying the signal strength so they appear to be coming from different locations and...wait a minute. I think my phone just got DOS'ed.
    - frandroid 12y ago
      That's a lot of money to DDOS people's phones at bus stops.
    - solipsism 12y ago
      You will never stop DOSs. It's trivial (I imagine, can't think why it wouldn't be) to DOS someone's cell signal. Allowing users to see which items are "certified real" and not raspberry pis in bushes is an easy engineering problem we've solved in a number of different contexts.
    - csuwldcat 12y ago
      The addition/counter to the Physical Web proposal I have been discussing with Google prevents these kinds of security issues in many locations/places: meet Geo-Origins --> https://github.com/csuwildcat/geo-origins/blob/master/explainer.md https://github.com/csuwildcat/geo-origins/blob/master/explai...
  - TeMPOraL 12y ago
    I don't think so. I think the proper analogy, that authors of the proposal have missed, is not search & spam, it's ATM and skimmers. How do you know you're not inserting card into a scanner?... ... well, everything proves that most likely, you have no clue.
meemoo 12y ago
Jon Nordby demoed this idea with http://flowhub.io/ http://flowhub.io/ a couple of weeks ago: http://youtu.be/wCdKukf-dHI http://youtu.be/wCdKukf-dHI 1. Tap tablet to Raspberry Pi with NFC tag 2. Pi serves Flowhub IDE (noflo-ui) with the currently-running graph, ready for editing This demo drops you directly into the source, but could easily have an interface layer first. It's just a link.

garethadams 12y ago

There's no reason it couldn't mean that anyway - if a device is open to the Internet then the URL it serves via Physical Web could easily be its own. But it allows for less-smart devices too. The biggest problem I can see, as with all proximity devices, is spoofing. How do I know the item listed as "Bus Stop" is actually the bus stop, and not someone's malicious Raspberry Pi hidden in the bush next to it?

tetrep 12y ago
>How do I know the item listed as "Bus Stop" is actually the bus stop, and not someone's malicious Raspberry Pi hidden in the bush next to it? The same way you know that top search results are accurate for a given word/phrase. As stated multiple times throughout the introduction[1] the solution for filtering out spam will probably have an implementation similar to internet search engines. [1]: https://github.com/google/physical-web/blob/master/documentation/introduction.md https://github.com/google/physical-web/blob/master/documenta...
- donutz 12y ago
  How do I know the top 100 items listed as "Bus Stop" aren't someone's malicious raspberry pi hidden in the bushes, spitting out hundreds of URLs and varying the signal strength so they appear to be coming from different locations and...wait a minute. I think my phone just got DOS'ed.
  - frandroid 12y ago
    That's a lot of money to DDOS people's phones at bus stops.
  - solipsism 12y ago
    You will never stop DOSs. It's trivial (I imagine, can't think why it wouldn't be) to DOS someone's cell signal. Allowing users to see which items are "certified real" and not raspberry pis in bushes is an easy engineering problem we've solved in a number of different contexts.
  - csuwldcat 12y ago
    The addition/counter to the Physical Web proposal I have been discussing with Google prevents these kinds of security issues in many locations/places: meet Geo-Origins --> https://github.com/csuwildcat/geo-origins/blob/master/explainer.md https://github.com/csuwildcat/geo-origins/blob/master/explai...
- TeMPOraL 12y ago
  I don't think so. I think the proper analogy, that authors of the proposal have missed, is not search & spam, it's ATM and skimmers. How do you know you're not inserting card into a scanner?... ... well, everything proves that most likely, you have no clue.

meemoo 12y ago

Jon Nordby demoed this idea with http://flowhub.io/ http://flowhub.io/ a couple of weeks ago: http://youtu.be/wCdKukf-dHI http://youtu.be/wCdKukf-dHI 1. Tap tablet to Raspberry Pi with NFC tag 2. Pi serves Flowhub IDE (noflo-ui) with the currently-running graph, ready for editing This demo drops you directly into the source, but could easily have an interface layer first. It's just a link.