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

Rather than IoT, I'd like to have networked Things under my control. The problem is not that they're networked but that they all want to phone home to central services.


I use a few IoT devices, and have them on a non-internet network. Unfortunately it requires me looking into each product first to see if it phones home, and deciding which features I want to give up by blocking that.


Well, at least most of the protocols are really really easy to RE.


Agreed...further, I'd want to be able to turn them off, easily...I'm stingy with bandwidth and giving away data related to my personal preferences...

The only feature I want (or really need) in an "appliance" , of any sort, is easy access to diagnostics if it fails...

I'd prefer appliances with something like OBD (II, III), installed in automobiles...


May I give a "collector's" point of view? I recently added a sort of phone home functionality to an app that runs on the client's network and the only goal here is to ensure that the people who use the software get value out of it. It helps me decide what to focus on and what matters to the customers.

It's not a substitute for picking up the phone, but it allows me to have more meaningful conversations when I do so.


An Intranet of Things?


Yes. But then most of the monetization opportunity is gone for the makers. Here is an opportunity for kickstarter and open source things to shine.




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

Search: