{"id":2314,"date":"2015-01-17T15:32:10","date_gmt":"2015-01-17T23:32:10","guid":{"rendered":"http:\/\/upon2020.com\/blog\/?p=2314"},"modified":"2015-01-17T15:32:10","modified_gmt":"2015-01-17T23:32:10","slug":"doc-searls-clouds-for-things-yes-please-but","status":"publish","type":"post","link":"https:\/\/upon2020.com\/blog\/2015\/01\/doc-searls-clouds-for-things-yes-please-but\/","title":{"rendered":"Doc Searls&#8217; Clouds For Things: Yes, Please, But!"},"content":{"rendered":"<p>My friend <a href=\"http:\/\/blogs.law.harvard.edu\/vrm\/2015\/01\/17\/the-answer-is-cft-clouds-for-things\/\">Doc Searls describes<\/a> the benefits of having an electronic place online for everyday things. He calls that place for a thing a &#8220;Cloud For Things&#8221;. For example:<\/p>\n<blockquote><p>The house where I\u2019m a guest in London has clouds for all its appliances. All the clouds are physical. Here they are:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/blogs.law.harvard.edu\/vrm\/files\/2014\/12\/2014_12_17_kingsroad-cloud_2a.jpg\" width=\"900\" height=\"568\" class=\"aligncenter\" \/><\/p>\n<p>Each envelope contains installation and instruction manuals, warranty information and other useful stuff.<\/p>\n<p>Now let\u2019s imagine a simple  digital container for each appliance\u2019s information: its own cloud. In form and use, it would be as simple and standard as a file folder.\n<\/p><\/blockquote>\n<p>I&#8217;m totally in agreement that this would be really useful, and I wholeheartedly support the idea. I&#8217;d love to have it for all of my things in my house!<\/p>\n<p>But there&#8217;s a big <strong>But<\/strong>. The But is that that &#8220;cloud&#8221; must not owned\/controlled by the vendor of the thing after the thing has been sold to me. It must change ownership, i.e. full control, from the vendor to me, when I buy the thing, and it must move with the thing if I sell the thing to somebody else.<\/p>\n<p>Why? It&#8217;s because if the thing&#8217;s electronic twin remains under control of the vendor, we end up with the all-so-pervasive Overlord architecture for the Internet of Things, where we never actually own anything, although we paid for it. My favorite example being the Nest thermostat, which we supposedly &#8220;buy&#8221; but over whose behavior we have no control, and which will stop working once we disagree with its terms of service. (Note: if there are terms of service for something, we don&#8217;t own it!)<\/p>\n<p>Coincidentally I&#8217;ll be talking about the contrast of the Overlord architecture for the internet of things, and what I call the &#8220;Indie IoT&#8221; this Tuesday at the <a href=\"http:\/\/www.meetup.com\/IoTSiliconValley\/events\/219724427\/\">Silicon Valley IoT Meetup<\/a>. The essence of Indie IoT is that the &#8220;clouds&#8221; for the things are independent from the vendor, and owned and controlled by the owner of the thing. They have many advantages, from privacy to being a much better platform for innovation.<\/p>\n<p>Turns out that only the Indie IoT architecture can actually deliver many of the benefits that Doc sees in his Clouds For Things proposal: customers helping customers, uncensored, reduced customer support costs and so forth. If the vendor remains the Overlord (&#8220;Ha, these clouds allow me to dictate\/upsell\/advertise to the customer even after the sale&#8221;), customers won&#8217;t use them, and the whole effort is for naught.<\/p>\n<p>Unfortunately, also, we do not have the entire technology in the market necessary for white goods vendors to actually deploy such Indie IoT clouds for things. (&#8220;How does the vendor initiate that cloud, and then transfer control, including root password, to the customer?&#8221;) But with things such as <a href=\"http:\/\/personal-clouds.org\/\">Personal Clouds<\/a>, Linux distros such as <a href=\"http:\/\/ubos.net\/\">UBOS<\/a>, and personal servers such as <a href=\"http:\/\/indiecomputing.com\/c\/indie-box-one\/\">Indie Box<\/a>, we will get there and it won&#8217;t be very long!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>My friend Doc Searls describes the benefits of having an electronic place online for everyday things. He calls that place for a thing a &#8220;Cloud For Things&#8221;. For example: The house where I\u2019m a guest in London has clouds for all its appliances. All the clouds are physical. Here they are: Each envelope contains installation&hellip;<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"webmentions_disabled":false,"footnotes":""},"categories":[67],"tags":[],"class_list":["post-2314","post","type-post","status-publish","format-standard","hentry","category-uncategorized","kind-"],"kind":false,"_links":{"self":[{"href":"https:\/\/upon2020.com\/blog\/wp-json\/wp\/v2\/posts\/2314","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/upon2020.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/upon2020.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/upon2020.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/upon2020.com\/blog\/wp-json\/wp\/v2\/comments?post=2314"}],"version-history":[{"count":5,"href":"https:\/\/upon2020.com\/blog\/wp-json\/wp\/v2\/posts\/2314\/revisions"}],"predecessor-version":[{"id":2319,"href":"https:\/\/upon2020.com\/blog\/wp-json\/wp\/v2\/posts\/2314\/revisions\/2319"}],"wp:attachment":[{"href":"https:\/\/upon2020.com\/blog\/wp-json\/wp\/v2\/media?parent=2314"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/upon2020.com\/blog\/wp-json\/wp\/v2\/categories?post=2314"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/upon2020.com\/blog\/wp-json\/wp\/v2\/tags?post=2314"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}