I don't know about the US, but where I live speed camera are relatively large bright colored boxes with reflective stripes on the side of the road, with mandatory "speed camera ahead" warnings.
Most of them are empty but people unfamliar with the place will usually slow down.
The laws are state and local. In AZ it's a city or township, then the people put it on the ballot and it gets shut down. Tucson voted 65% no cameras, and later we got a state wide ban on highways, so it's a still a work in progress. The tickets are civil law, so you can throw it out, frame it, or make a coffee table book if you get enough:)
This, windows phone works well as a phone, but the lack of quality apps and crappy browser that chokes/crashes on avertising make the "smart" part a complete fail.
How/why would a production car need to process it differently and why couldn't all processing be done in real time? Safety certification means the car's functionality has to be static, until the next certified software update. Data does not need to leave the car, since the purpose of the data is for the car to drive, which is a transient state.
If you're driving a production car version 1.23, then the manufacturer (obviously) wants data from that car to be used in development of production car version 1.24.
The technology needs improvements, and the process of making those improvements is hungry for data. Every manufacturer will be in development/debug mode of their self-driving systems at least for the coming decade, so sensor data from every mile of every car is wanted and useful, and manufacturers are configuring production cars to upload as much raw sensor data as is practical.
That logic applies to every product ever made in the history of technology. Somehow their R&D departments did not need 7x24 data feeds.
Each society can decide whether to permit this particular product to collect unlimited data. The presumption is that the data belongs to no one. Let's see what happens when more than one large corporate entity lays competing claim to the same data subset, embedded by a wide-ranging data dragnet.
I do think that the logic does not apply to every product ever made, that there's a major conceptual difference between products purely designed by humans and products where key features are driven by machine learning and availability of raw data.
A 24/7 data feed from your toaster is not going to make your toaster better. It might help an R&D department identify some ways how the next toaster model should be different, but that's about it.
However, a self driving car is data-starved and is still going to be data-starved years from now. At any moment of time, your car could drive better and safer simply if it had more "experience" - the v1.24 software release can be meaningfully better than the v1.23 software release even if R&D department does nothing else but simply import the data received from millions of other cars; if your car is allowed to learn from what other cars saw.
Ensuring that the quality of driving systems increases as fast as it can is important for the society, with a major impact on injuries and casualties. I feel that it would be best for the society if we ensure that this learning (and the required data transfer) is not prohibited, as long as we can solve/restrict the potentially harmful uses of the data.
Or maybe we could save more lives by using technology to augment human drivers?
We don't actually know that self-driving cars are possible in unrestricted environments. The industry is asking for highly invasive surveillance but has no liability for failure to deliver. What happens if "more data" turns out to be insufficient? Will the next request be "restrict the environmental context" or "pass new laws to change human behavior"? Where does it end? Other industries have to deliver results before changing the market. Uber et al promised the moon to their investors, then ignored local laws, then promise to save lives, then ignore privacy concerns, then ..?
No. That's not what I'm talking about. That's just a way to host your own snapshot of the entire npm registry. Not a good way to introduce the decentralization feature of IPFS.
