IoT’s killer app is not home security
I think the article does a decent job of highlighting some of (what I hear as) the primary concerns surrounding IoT, namely:<p>1. WiFi needs to always work<p>2. Internet connection needs to always work<p>3. Power needs to always work<p>4. Stability of software and firmware<p>5. Trustworthiness of software and firmware (including data leakage, privacy, etc)<p>Simultaneously, though it rightly points out that IoT is still very much in its infancy, I think it misses a very important observation: there will absolutely come a day when IoT is unavoidable. Not as in you can&#x27;t avoid encountering it, but as in you can&#x27;t avoid <i>owning</i> it. There will, (I think anyways) without a doubt, be a day when devices that the average Western consumer considers necessary for everyday life -- things like refrigerators, electric meters, thermostats, and so on -- are effectively impossible to buy &quot;dumb&quot;. Every analysis and meta-analysis of IoT that I&#x27;ve seen has been incredibly bullish on it, and I think that&#x27;s an indication of how much economic incentive there is for it. Given that, I&#x27;d say automobile ECIs are the proof in the pudding for the assertion that IoT will be unavoidably ubiquitous. As an experiment, try to find a new car that you can personally can actually buy, that doesn&#x27;t have a computer in it. As the median Western consumer, that&#x27;s not possible. So I&#x27;m pretty convinced that for IoT, non-participation will not remain an option.<p>So then the question is, what do we do about those 5 issues? I tend to look at stuff like this from an economic perspective; clearly device producers haven&#x27;t seen enough market pressure to give a shit about any of them. Right now, the only pressure device creators are demonstrating is a profound push to get something, anything, to market. It really is an internet of shit.<p>That being said, even the bare minimum is really hard here. You&#x27;re talking about a system architecture that our existing infrastructure simply isn&#x27;t cut out to handle. Think about the challenges involved in deploying a reliable authentication system to a web-scale application, and now imagine doing it in a way that can&#x27;t necessarily rely upon a central server. It&#x27;s far easier to just &quot;punt&quot; on the second half of that, assume the traditional web paradigm (trusted third party server), and call it a day. And make no mistake, for a commercial device, authentication is absolutely required, even for home WiFi network: not everyone wants every person in their house to control, for example, their locks. Or, alternatively, imagine an AirBNB host being forced to give their guests unfettered access to their IoT vibrator (yes, they exist). These edge cases are everywhere, and they make authentication of some sort or another an absolute requirement.<p>My hope is that someone (and by someone, in all honesty I&#x27;m talking about my own project [1]) can come along and say to device producers:<p>1. I understand how hard it is for you to make <i>any</i> IoT device.<p>2. I&#x27;m going to make it substantially cheaper for you to do that, but...<p>3. The privacy and security I&#x27;ve baked into my system is inseparable from your economic benefit as a device producer.<p>The idea is to evolve that into:<p>4. You cannot be competitive in the IoT marketplace without privacy and security.<p>At this point, with how completely and totally horrendous the industry has been in these areas so far, I think that&#x27;s the only viable way we can achieve those goals without a tremendous amount of growing pains.<p>[1] The project is called Hypergolix, and at this point it&#x27;s basically &quot;Dropbox for Python objects, geared towards IoT, with an emphasis on social, and secured via end-to-end encryption&quot;. We&#x27;re in the process of getting a private alpha shippable, to be followed soon by a public alpha. It all works, and it&#x27;s all open source, but there&#x27;s some necessary stuff we need to iron out in the coming weeks. Our outdated landing page is <a href="https:&#x2F;&#x2F;hypergolix.com" rel="nofollow">https:&#x2F;&#x2F;hypergolix.com</a>, but a better preview of the developer experience is on our very incomplete docs page: <a href="http:&#x2F;&#x2F;pyhgx.readthedocs.io&#x2F;en&#x2F;latest&#x2F;index.html" rel="nofollow">http:&#x2F;&#x2F;pyhgx.readthedocs.io&#x2F;en&#x2F;latest&#x2F;index.html</a> . The whole project is backed by a crypto protocol known as Golix: <a href="https:&#x2F;&#x2F;github.com&#x2F;Muterra&#x2F;doc-golix" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Muterra&#x2F;doc-golix</a>