Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Don't get me wrong I totally get it. When you plug your device into a message bus like you would a power cord into the wall, things begin to make sense.

Here is how I see it coming together:

- STANDARDS: The "message bus" needs to have essentially an HTTP protocol standard, that both producers and receivers on both ends can understand.

- Hardware, appliances and objects generate their own implementation of an end-node adhering to the protocol.

- Wifi Routers allow the firmware to run "master" nodes, that would have a mobile app and a web front end to configure and customize.

But because having to VPN into your house to manage anything, or even have to have a VPN at all would be silly. So now we host it in the cloud and the devices simply pull.

To design the APIs, platform, SDK, and hosting solution would look a lot like what Apple and Google are doing with their all-encompassing themed keynotes this year. I'm actually worried about interoperability more than anything.



>STANDARDS: The "message bus" needs to have essentially an HTTP protocol standard, that both producers and receivers on both ends can understand.

I think a better analogy to what we need should be an HTTPS protocol standard. HTTP was designed in an era of slow computers when security and privacy were not particularly high on the list of developer priorities, and now we're seeing an agonizingly slow move towards universal HTTPS adoption. It'd be nice to actually start out with security-aware protocols for once.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: