|
|
March 7 · Issue #16 · View online |
|
Hi, welcome to another week with the Observatory. In this issue: Terms of Service governance, Voice ID for assistants, Self-driving beta tests, and faulty smart meters.
|
|
|
Last week, it transpired that UBER had a system in place to automatically flag city officials who were trying to enforce local laws and regulation by looking for patterns, such as credit cards that could be linked back to city governments. This was part, as told by UBER, of a wider effort, called VTOS, for âViolation of Terms of Serviceâ. This is part of a wider concern Iâm looking at with Internet of People. How does the widespread diffusion of Terms of Services into goods that were previously unencumbered by them, but instead regulated by law, affect the position of customers. Iâve written before how inclusion of software in traditional goods, and thus the inclusion of licenses and Terms of Service in the sale contract, reduce the optionality users have with regards to the goods bought. We need to have a look at what Ownership means in a world of connected products. This discussion flared up again this week with the discussion around âRight to Repairâ legislation in Nebraska. Interestingly, itâs farmers again who lead the charge for a more liberal approach to technology, after John Deere and its farm equipment pretty much stood in as primary case for the section 1201 DMCA exemption pertaining to vehicles. The broader issue here is that we have very granular legislation and regulation around many areas of commerce and life. Automotive traffic is regulated differently than Entertainment for a reason. With the increasing diffusion of technology and software into all kinds of arenas, this granularity gives way to more generalised software governance, and regulation made in on area often have unanticipated and counterproductive effects in other areas. That legislation crafted to notionally defeat music piracy has an effect on farmers trying to service their equipment is not something that any of the sponsors of the DMCA would have foreseen. UBER provides an interesting illustration of this problem, and shows that this is not just something related to physical objects powered by software, but platform services in general. The question here is, when local laws and Uberâs terms of service conflict, which prevails? The local officials assumed, naively, that laws trumped terms of service. But that is antiquated thinking. In the modern era of global technological capitalism, the terms of service need to prevail universally. Otherwise youâd just have anarchy. I mean, I guess I am kidding, but Uber probably believes that.
|
|
Finally. I try not to use that word too often, but it appears that Amazonâs Alexa system might finally get voice fingerprinting capabilities. Iâve long argued that this is an essential feature for down-the-line capabilities, such as being usable in multi-user homes. And itâs a basic security feature. If we want our voice-activated systems to be generally more helpful, they need to be able to respond to appropriate context, e.g. not giving just about anyone who happens to be within pick-up distance of the mic array access to my calendar, or to the IoT-enabled smart locks that might be hooked up to the system. Given the murder case we discussed last week, and Alexaâs potential role as evidence, it becomes even more pressing then, that Amazon reconsider their approach to storing voice snippets, given that, with Voice Fingerprinting, theyâre then going to be tagged with a unique user ID. Apple gets a lot of flak for ânot playingâ in the voice activated assistants arena, and for their privacy rules to make it cumbersome to effectively develop for the platform. But with these concerns, the decision to limit the amounts of data stored with the firm looks like it might indeed build up to a competitive advantage. In other news: have you heard AWS went down? You might have noticed that a few web services were offline late last week. Which of course leads the pundits to declare this is a gaping problem with the Internet of Things, whereas when the cloud goes offline, stuff becomes unusable. The only problem: there are no cases to report where this happened. Iâve so far found one example where a user was prevented to do something with their smart home, and then again, that was a problem of IFTTT being down, not with the actual device. But yâknow, why let facts get in the way of a good opinion. Lastly, I talk a lot about how startups fulfil the macro job of discovering new products. They donât necessarily have to make sense on their own, as long as someone thinks itâs an interesting enough bet that could pay off. And a lot of success stories have started as weird and have been cast aside as toys. And then, every so often, I stumble upon something that makes me question this view. This week, it was the Internet-connected condom. Software is eating the world, indeed.
|
|
Ouch. Smart Meters are often considered a fundamental building block for more flexible energy systems that allow large amounts of power from renewable energy sources. They are not uncontroversial. Concerns range from privacy impact to security scenarios. What wasnât really on anyones mind, however, is that the meters could deliver just plain wrong readings. But such is the case of about 750k smart meters in the Netherlands. The effects of wrong readings donât just impact customers, which might charged to much (or too little, the article really doesnât say) but negates the value of dynamically regulating the power grid. Correct data is really important here, and if you canât trust the meters, well, then youâre pretty much SOL. Another important component of more flexible grids is storage. Here, weâve made tremendous advances in the affordability of Li-Ion batteries, primarily driven by e-mobility and the smart phone revolution. Now the decreasing cost curve comes home to bite, in a situation that might ring familiar to anyone whoâs followed the fate of German photovoltaics producers: Teslaâs batteries are already being underpriced, before the full Gigafactory has even come online. Such is the nature of exponentials.
|
|
Self-piloted cars work great in contained environments. Out in the real world, where you might encounter inclement weather or construction sites? Well, the jury is still out, but right now, it doesnât look too hot. Thereâs the case of a Tesla driver, ceding control to the Autopilot which promptly slams the car into a concrete barrier. The lane markings hadnât been adjusted. The reality of street traffic, even in relatively predictable situations like highways, remains messy. And messiness is the nemesis of algorithms. Given that Tesla accident, thereâs been discussion on how the construction crews should have adjusted the lane markings, or how the Autopilot system shouldâve warned the driver that it wonât be able to handle the situation correctly. There is a case for the former, but given that for a human driver, the situation was pretty obvious, there probably wasnât a perceived need to do that. The latter is harder. An algorithm cannot reliably predict when the operational circumstances will outstrip its ability to adapt. Thatâs why the problem of ceding control from autonomous driving back to human operation remains such a big one. What weâre left with is the impression that Teslaâs Autopilot is indeed a glorified beta test, that customers pay good money for to participate in. And self-driving is just one part of the changes that the automotive industry currently experiences. Another area is software platformisation, and where all that software thatâs necessary to make those rolling computers work and enjoyable to use actually lives. BMW put the boot down not supporting Android Auto. That might be just economic signaling, but expect the heat to increase in what looks to shape up to be another platform war.
|
|
|
|
Phew, what a week. Iâm hunkering down to finish a couple of research jobs that have lined up. Iâm likely going to be in DĂźsseldorf next week. If youâre in the area, we should have a coffee. And if youâre at Bosch Connected World next week, give me a shout so we can meet. See you next week! Cheers, Martin
|
Did you enjoy this issue?
|
|
|
|
In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
|
|
|
|
|
|