Also, I'd imagine there's a big difference in insurance costs between hiring college grads and high school grads. I mean, I've never shopped for commercial car insurance, so I can't be sure, but....
There are no pedestrians in Santa Clara or Mountain View. I'm serious.
... spoken like someone who has never driven down Charleston Rd. through the Google campus. Imagine streams of pedestrians flooding across the roads (mostly at traffic lights, but not always), brightly colored bicycles every twenty feet (both in the bike lane and not), etc. It's a self-driving-car safety testing dream.
That's not really true. In a studio environment, when you're doing pitch correction, the pitch detection is more accurate at higher sampling rates because of the bin size of an FFT. I suspect that there are probably advantages for other operations like convolution, given how radically different the results often sound at different sampling rates.
Additionally, human hearing doesn't top out at 20 kHz. Adult hearing usually falls off way below that, and by the time it hits 20 kHz, most adults can't hear anything at all, but some people have the ability to hear loud sounds well past 22 kHz. There's usually nothing of value up there, but certain instruments (cymbals in particular) sound decidedly different if you roll off at or below 20 kHz (which you need to do if you're sampling at only 44.1 kHz to avoid aliasing artifacts near the sampling rate). That's why 48 kHz is the gold standard for audio, not 44.1 kHz. CD audio sample rates have aways been a compromise.
sure, fucking great, let's just take a chance on another polio epidemic. Why the fuck not, the antivaxxers have already brought back measles and mumps outbreaks that were stamped out since my childhood (1950s).
Measles wasn't officially "eliminated" in the U.S. until 1997. Worse, "eliminated" in this context just means "fewer than one case per 1 million people". With 300 million people in this country, that's still potentially many hundreds of cases every year, and that was before the anti-vaxxers made things worse. You'll find similar statistics for mumps. Neither has ever reached or even approached zero cases per year in the U.S., as far as I'm aware, much less in the rest of the world, and IMO, you shouldn't even consider stopping a vaccine until a disease has had zero cases in the U.S. for several years in a row.
However, polio meets that criterion and then some. The last case of polio getting caught "in the wild" by someone while inside the U.S. was in 1979 (*). During the two decades that followed, there were a total of eight cases of people bringing polio in from overseas, and the last imported case of polio was way back in 1993; the last case before that one was in 1986. So there have been literally zero (*) polio cases in the U.S. for over twenty years, and only only one in the past thirty years.
* These stats are pedantically incomplete, because they only cover natural cases of polio. Officially, between 1980 and 1999, there were 162 polio cases in the U.S. However, 154 of them were cases of vaccine-associated paralytic poliomyelitis (VAPP) or vaccine-derived polioviorus (VPDP). It is worth noting that the oral polio vaccine responsible for those illnesses is no longer administered in the United States, precisely because it was causing orders of magnitude more cases of polio than it prevented. Since the eradication of the oral vaccine in 2000, there have been zero polio cases in the U.S.
To put polio's numbers in even better perspective, there were only 74 polio cases in 2015 worldwide—mostly in countries whose water quality is far below what it should be by modern standards. This means you're about 3,000x more likely to get leprosy. You're about twice as likely to die from heart complications arising from dental cavities. And so on. So although polio hasn't quite been eradicated worldwide, it is so close to completely gone that the notion of polio resurfacing in the U.S. seems borderline absurd at this point.
What could possibly go wrong?
Realistically? Not much. Like I said... Bigfoot. No, make that Bigfoot having inappropriate relations with a unicorn.
At an absolute minimum, we should be seriously talking about the phase-out period. It really makes no sense for every child born in the U.S. to be vaccinated for a disease that only affects tens of people worldwide and has less than a 1% rate of serious complications even in the astoundingly unlikely event that it somehow made it to the U.S. and managed to be transmitted in spite of our modern sewage system and modern medical system.
In truth, they anti-vaxxers might be nutters, but that doesn't mean they're 100% wrong. There is reason to be cautious about over-vaccinating people, particularly for diseases that are extremely uncommon and/or for which the vaccine has a low rate of effectiveness, if only because of the slightly elevated cancer risk involved.
For example, polio is considered eradicated in the U.S., but it is still part of the mandatory vaccine regimen. At this point, wild polio exists in only about three countries in the world. You're almost as likely to see Bigfoot as you are to catch polio in the U.S., even if you aren't vaccinated. So we should probably be tapering off those vaccines by now, and it probably won't hurt to allow parents to opt out of that one if they choose to do so. Then again, as an inactivated virus, the risk is small enough that it is probably harmless, so... whatever.
Personally, I blame Adobe for deciding to stop selling software and forcing everybody to rent it. I'm still using Photoshop CS6, and gradually transitioning new content creation away from Adobe products in expectation that eventually I'll have to treat it as a legacy application and run it in a virtual machine when a future OS update breaks it.
This. If Amazon wants people to take it seriously in this space, you have to actually get something of value for that extra $15. You know, like a way to replace the battery. I was ready to order one until I saw that bit. If I'm going to buy something where the hardware is just going to fail in a few months, then it will always be a lousy hack, and I might as well save $15 and make it an only slightly bigger hack by using the standard buttons and sniffing the packets.
That's pretty much accurate. However, there actually is another alternative, if you're starting a company: Locate yourself in one of the suburbs where workers fleeing the high cost of living relocate. For example, near the Silicon Valley, you have at least four areas to consider:
Santa Cruz/Watsonville
Monterey/Salinas
Sacramento/Elk Grove
Morgan Hill/Gilroy
These areas have lots of tech workers who commute into the valley every day. Most of these areas have almost no tech companies. That means that these areas are extremely viable as locations for tech companies, because you have pent-up demand for tech employment, and in the unlikely event that you exhaust the local workforce, you're close enough to draw in commuters from SV.
Watsonville is a particularly good location, because you get reverse commutes from SV and Santa Cruz, and a shorter commute for people in Watsonville, Salinas, Monterey, Gilroy, or Morgan Hill. If more companies would locate/relocate there, traffic on Bay Area freeways would diminish considerably. Also, land is relatively cheap.
Repealing Prohibition only accomplished one thing: It just replaced one set of problems (police spending too much time chasing after bootleggers) with an even worse problem. In just one decade, 2001 to 2010, there were more than 100,000 alcohol related fatalities. Since the end of prohibition, I'll bet the total number of alcohol related deaths is near 1 million.
Now let's put that number in perspective. Every year, there are 2.6 million deaths in the United States, or about 26 million over that ten-year period. So alcohol is the cause of only about four tenths of one percent of deaths in the U.S.
Besides, we're talking about pot. It doesn't matter how slow your reaction time is if you're driving at 5 MPH down the shoulder with your windows down and your blinkers on.
They're reporting that an electric vehicle, which breaks mainly through electromagnet resistance used to regenerate electrical power, produces more break dust than a gasoline powered vehicle that uses breaks.
Regenerative braking isn't exclusive to EVs. You can also use it on hybrids, which presumably weigh a lot less than an EV.
I'm not saying that this story isn't full of crap—it probably is—but....
Ha, ha. You still think those vulnerabilities were accidents.
IMO, it seems far more likely that the SQL injection holes were deliberate. After all, parameterized SQL queries have been the norm for at least eight or ten years, which means that for this to be accidental, either the software would have to be as old as Windows Vista or the developers would have to be so grossly incompetent that they would never be able to hold down a job writing database software for more than a week or two.
The whole "never attribute to malice" thing applies only when it can be plausibly attributed to incompetence. SQL injections in an election system in 2016 fall so far on the other side of that line that you can't even see the line from there.
With that said, in the unlikely event that I'm wrong, and that it really was caused by a grossly incompetent vendor, I expect to see that vendor added to a government blacklist and become immediately ineligible for any government contracts going forward. I also expect to see the software in question thrown away and paper ballots used until such time as a suitable replacement can be found. There's no excuse for allowing software that doesn't even meet 2010-era standards to be used for running elections in 2016. None whatsoever.
And another liberal demonstrates that it's just a short road from liberalism to fascism. No ideas allowed that don't resonate in the echo chamber.
Suppress != block
What you're missing here is just how loud the conservative echo chamber is. If every story that resonates in the conservative echo chamber were allowed to trend on Facebook, it would overwhelm non-conservative ideas, because, to be frank, the conservative side of the house has a tendency to scream louder than the liberal side, and in ways that are much more deliberate and extreme in their use of rhetoric to drive the people into a panicked frenzy. Were that input not partially suppressed, Facebook would become just another echo chamber, rather than a medium for the free exchange of ideas.
So in effect, Facebook is using bias to ensure that the overall content remains fair and unbiased, by preventing those who scream the loudest from being heard disproportionately.
What you describe likewise falls into the category "because DNS-SD doesn't support a PKI yet". If it did, browsers would be updated to trust it for the local TLD.
I don't think PKI is really feasible for.local, because the definition of what is trusted for.local depends on what network you're using. I'm more than willing to trust certain arbitrary signing certs at work, but that doesn't mean I want to trust those signing certs if they suddenly show up on a server on some other network in the wild.
Until then, it's easier to apply a trust-on-first-use model, like that used by SSH, through the "add exception" button that browsers show for an untrusted issuer.
That's better than nothing, but in an ideal world, there would be some semi-out-of-band handshake-based pairing mechanism whereby you connect to the host, the host returns a credential, the browser rejects it and sends a challenge, and it displays the challenge on its screen. You type the challenge into your browser. Use EC or DH to exchange the challenge to make MITM impractical. Maybe also use BTLE or even RFID or NFC for parts of the handshake, thus ensuring that the devices must be a few inches apart and providing a second, semi-secure channel in parallel, minimizing the risk of both being compromised at once, and possibly making the process almost completely transparent to the user. (Touch the device to your computer, and poof, instant secure connection.)
The device generates a self-signed certificate, the user manually verifies the key fingerprint out of band on the exception screen, and the browser adds it to the list of user-vetted certificates.
Realistically, the user verifies only the first and last few digits, making it pretty easy to attack even most tech-savvy users. Besides, that would require a screen on the device that's big enough to show a key fingerprint. That's not always practical.
From all information I overlook I can say, yes in "C" it is incredible easy to make simple errors with hugh consequences - choosing types for example. However "C"-programming can be made more secure with a strict application of certain rules especially on "forbidden" & dangerous constructions. The missconception why "C" is deemed as an insecure language is that much of the code in use stems from the "ancient" times, when such code was mostly not exposed to the raw unforgiving "force" of the internet.
This—in much the same way that the huge number of PHP SQL injection attacks is not because PHP's SQL APIs are insecure, but rather because so much code is still around that was built against early APIs that lacked modern security features like template-based queries. Eventually, every language gets these sorts of complaints, and always for the same reason; most code out there is in a constant state of "deprecated, but still works, so we aren't going to touch it".
5. Multiple gas cans in a single vehicle are much more likely to reach that ratio, and over a larger area as well.
This is where we disagree. The probability of a gas can's fuel-air ratio being ideal for ignition is exactly the same whether that gas can is next to another one or not. So although the probability of that specific vehicle catching fire is twenty times higher if it has twenty gas cans, the company that owns the vehicle has exactly the same chance of having a vehicle catch fire, because the probability does not decrease by adding more vehicles; it merely gets spread out over a larger number of death traps^H^H^H^H^H^H^H^H^H^H^Hvehicles.
6. A 10 gallon fuel fire is bad enough, a 200 gallon fuel fire is quite another. Note, I'm not including the vehicle's fuel tank because, on consideration, it's generally pretty well protected.
I was assuming more like a few 5-gallon cans per vehicle—say 25 to 30 gallons in total. Two-hundred gallons would be insane. A typical half-ton pickup can't even carry that much weight; that would exceed its maximum bed weight by about 250 pounds, not counting the gasoline tanks. Besides, tanks over 25 gallons have lots of additional regulations, and most cities' fire codes won't let you store more than 25-30 gasoline cans in a single home or business, so if you go over that limit, you'd never be able to legally park the vehicle overnight....
That argument could be made for a pretty wide variety of stuff from sugar to alcohol.
Not really. Sugar plays a vital role in sports drinks, and moderate consumption of some alcoholic beverages has been shown to have a number of health benefits, including lower risk of heart disease.
You left out one, and it's a pretty big one. By policy, no certificate authority is allowed to issue a TLS certificate for any host in the.local domain, because there's no ownership/legitimate control over those domains, multiple people could legitimately lay claim to the same domains on different networks, and the domain names are chosen by random end users who don't even know what a TLS certificate is, much less how to buy their own domain name. Therefore, any Wi-Fi-connected device that needs to serve content via DNS service discovery must currently use an unencrypted connection.
IMO, that's a rather serious flaw in the notion of requiring HTTPS everywhere. Unlike the issues you listed, which all fall into the category of "because X hasn't upgraded Y yet" or "because X hasn't bothered to support it yet", this one is actually a problem for which there is currently no solution, and any possible solution would require completely changing the way we think about site security, moving us from a strict central trust model to something much more flexible and decentralized.
Basically, until that problem is solved, the IoT is DOA as far as HTTPS is concerned.
In snowy weather, roads can lose a whole lane. Four lane roads become two lane roads become three lane roads. Watching a car subtlety veer as it runs over an ice patch, and knowing how to handle that (avoid the spot, coast over in neutral, whatever) is something that a good driver will do instantly, and a computer can't yet handle- nor does anyone seem to be working on that issue.
How is that anything more complicated than merely providing additional training data? I'm assuming that all self-driving cars will involve machine learning, no?
They don't typically whip out a hose and start pouring out pints, though.
Tow trucks do this all the time. In some places, the police do, too. It's hard to come up with a clear reason why one truck carrying twenty properly filled, properly made gas cans is that much less safe than twenty trucks carrying one.
I would think that the existing Coast Starlight line could be upgraded for HSR, so long as you divert inland a bit to bypass downtown SLO and Santa Barbara. It would, however, be at least a 30% longer trip (or even longer if they didn't bypass those downtown areas), and that's not factoring in the extra delay caused by going slowly around that one long, tight curve (maybe where it goes around the women's prison?). The bigger problem is that they'd have to convince Union Pacific to give them priority, which is almost certainly easier said than done. And the route would also be shared with the Coast Starlight, the Pacific Surfliner, Metrolink, and Caltrain....
Slashdot Mirror
Also, I'd imagine there's a big difference in insurance costs between hiring college grads and high school grads. I mean, I've never shopped for commercial car insurance, so I can't be sure, but....
... spoken like someone who has never driven down Charleston Rd. through the Google campus. Imagine streams of pedestrians flooding across the roads (mostly at traffic lights, but not always), brightly colored bicycles every twenty feet (both in the bike lane and not), etc. It's a self-driving-car safety testing dream.
That's not really true. In a studio environment, when you're doing pitch correction, the pitch detection is more accurate at higher sampling rates because of the bin size of an FFT. I suspect that there are probably advantages for other operations like convolution, given how radically different the results often sound at different sampling rates.
Additionally, human hearing doesn't top out at 20 kHz. Adult hearing usually falls off way below that, and by the time it hits 20 kHz, most adults can't hear anything at all, but some people have the ability to hear loud sounds well past 22 kHz. There's usually nothing of value up there, but certain instruments (cymbals in particular) sound decidedly different if you roll off at or below 20 kHz (which you need to do if you're sampling at only 44.1 kHz to avoid aliasing artifacts near the sampling rate). That's why 48 kHz is the gold standard for audio, not 44.1 kHz. CD audio sample rates have aways been a compromise.
Measles wasn't officially "eliminated" in the U.S. until 1997. Worse, "eliminated" in this context just means "fewer than one case per 1 million people". With 300 million people in this country, that's still potentially many hundreds of cases every year, and that was before the anti-vaxxers made things worse. You'll find similar statistics for mumps. Neither has ever reached or even approached zero cases per year in the U.S., as far as I'm aware, much less in the rest of the world, and IMO, you shouldn't even consider stopping a vaccine until a disease has had zero cases in the U.S. for several years in a row.
However, polio meets that criterion and then some. The last case of polio getting caught "in the wild" by someone while inside the U.S. was in 1979 (*). During the two decades that followed, there were a total of eight cases of people bringing polio in from overseas, and the last imported case of polio was way back in 1993; the last case before that one was in 1986. So there have been literally zero (*) polio cases in the U.S. for over twenty years, and only only one in the past thirty years.
* These stats are pedantically incomplete, because they only cover natural cases of polio. Officially, between 1980 and 1999, there were 162 polio cases in the U.S. However, 154 of them were cases of vaccine-associated paralytic poliomyelitis (VAPP) or vaccine-derived polioviorus (VPDP). It is worth noting that the oral polio vaccine responsible for those illnesses is no longer administered in the United States, precisely because it was causing orders of magnitude more cases of polio than it prevented. Since the eradication of the oral vaccine in 2000, there have been zero polio cases in the U.S.
To put polio's numbers in even better perspective, there were only 74 polio cases in 2015 worldwide—mostly in countries whose water quality is far below what it should be by modern standards. This means you're about 3,000x more likely to get leprosy. You're about twice as likely to die from heart complications arising from dental cavities. And so on. So although polio hasn't quite been eradicated worldwide, it is so close to completely gone that the notion of polio resurfacing in the U.S. seems borderline absurd at this point.
Realistically? Not much. Like I said... Bigfoot. No, make that Bigfoot having inappropriate relations with a unicorn.
At an absolute minimum, we should be seriously talking about the phase-out period. It really makes no sense for every child born in the U.S. to be vaccinated for a disease that only affects tens of people worldwide and has less than a 1% rate of serious complications even in the astoundingly unlikely event that it somehow made it to the U.S. and managed to be transmitted in spite of our modern sewage system and modern medical system.
In truth, they anti-vaxxers might be nutters, but that doesn't mean they're 100% wrong. There is reason to be cautious about over-vaccinating people, particularly for diseases that are extremely uncommon and/or for which the vaccine has a low rate of effectiveness, if only because of the slightly elevated cancer risk involved.
For example, polio is considered eradicated in the U.S., but it is still part of the mandatory vaccine regimen. At this point, wild polio exists in only about three countries in the world. You're almost as likely to see Bigfoot as you are to catch polio in the U.S., even if you aren't vaccinated. So we should probably be tapering off those vaccines by now, and it probably won't hurt to allow parents to opt out of that one if they choose to do so. Then again, as an inactivated virus, the risk is small enough that it is probably harmless, so... whatever.
Personally, I blame Adobe for deciding to stop selling software and forcing everybody to rent it. I'm still using Photoshop CS6, and gradually transitioning new content creation away from Adobe products in expectation that eventually I'll have to treat it as a legacy application and run it in a virtual machine when a future OS update breaks it.
This. If Amazon wants people to take it seriously in this space, you have to actually get something of value for that extra $15. You know, like a way to replace the battery. I was ready to order one until I saw that bit. If I'm going to buy something where the hardware is just going to fail in a few months, then it will always be a lousy hack, and I might as well save $15 and make it an only slightly bigger hack by using the standard buttons and sniffing the packets.
That's pretty much accurate. However, there actually is another alternative, if you're starting a company: Locate yourself in one of the suburbs where workers fleeing the high cost of living relocate. For example, near the Silicon Valley, you have at least four areas to consider:
These areas have lots of tech workers who commute into the valley every day. Most of these areas have almost no tech companies. That means that these areas are extremely viable as locations for tech companies, because you have pent-up demand for tech employment, and in the unlikely event that you exhaust the local workforce, you're close enough to draw in commuters from SV.
Watsonville is a particularly good location, because you get reverse commutes from SV and Santa Cruz, and a shorter commute for people in Watsonville, Salinas, Monterey, Gilroy, or Morgan Hill. If more companies would locate/relocate there, traffic on Bay Area freeways would diminish considerably. Also, land is relatively cheap.
There was an AC post between the GP's post and yours. You probably just don't see it because your view is filtered to not show posts with score 0.
Apple's app review, for one....
Now let's put that number in perspective. Every year, there are 2.6 million deaths in the United States, or about 26 million over that ten-year period. So alcohol is the cause of only about four tenths of one percent of deaths in the U.S.
Besides, we're talking about pot. It doesn't matter how slow your reaction time is if you're driving at 5 MPH down the shoulder with your windows down and your blinkers on.
Regenerative braking isn't exclusive to EVs. You can also use it on hybrids, which presumably weigh a lot less than an EV.
I'm not saying that this story isn't full of crap—it probably is—but....
Ha, ha. You still think those vulnerabilities were accidents.
IMO, it seems far more likely that the SQL injection holes were deliberate. After all, parameterized SQL queries have been the norm for at least eight or ten years, which means that for this to be accidental, either the software would have to be as old as Windows Vista or the developers would have to be so grossly incompetent that they would never be able to hold down a job writing database software for more than a week or two.
The whole "never attribute to malice" thing applies only when it can be plausibly attributed to incompetence. SQL injections in an election system in 2016 fall so far on the other side of that line that you can't even see the line from there.
With that said, in the unlikely event that I'm wrong, and that it really was caused by a grossly incompetent vendor, I expect to see that vendor added to a government blacklist and become immediately ineligible for any government contracts going forward. I also expect to see the software in question thrown away and paper ballots used until such time as a suitable replacement can be found. There's no excuse for allowing software that doesn't even meet 2010-era standards to be used for running elections in 2016. None whatsoever.
Suppress != block
What you're missing here is just how loud the conservative echo chamber is. If every story that resonates in the conservative echo chamber were allowed to trend on Facebook, it would overwhelm non-conservative ideas, because, to be frank, the conservative side of the house has a tendency to scream louder than the liberal side, and in ways that are much more deliberate and extreme in their use of rhetoric to drive the people into a panicked frenzy. Were that input not partially suppressed, Facebook would become just another echo chamber, rather than a medium for the free exchange of ideas.
So in effect, Facebook is using bias to ensure that the overall content remains fair and unbiased, by preventing those who scream the loudest from being heard disproportionately.
It's okay. They removed a vowel in the headline. No, wait, I don't think they did.... They just added an apostrophe.....
I don't think PKI is really feasible for .local, because the definition of what is trusted for .local depends on what network you're using. I'm more than willing to trust certain arbitrary signing certs at work, but that doesn't mean I want to trust those signing certs if they suddenly show up on a server on some other network in the wild.
That's better than nothing, but in an ideal world, there would be some semi-out-of-band handshake-based pairing mechanism whereby you connect to the host, the host returns a credential, the browser rejects it and sends a challenge, and it displays the challenge on its screen. You type the challenge into your browser. Use EC or DH to exchange the challenge to make MITM impractical. Maybe also use BTLE or even RFID or NFC for parts of the handshake, thus ensuring that the devices must be a few inches apart and providing a second, semi-secure channel in parallel, minimizing the risk of both being compromised at once, and possibly making the process almost completely transparent to the user. (Touch the device to your computer, and poof, instant secure connection.)
Realistically, the user verifies only the first and last few digits, making it pretty easy to attack even most tech-savvy users. Besides, that would require a screen on the device that's big enough to show a key fingerprint. That's not always practical.
This—in much the same way that the huge number of PHP SQL injection attacks is not because PHP's SQL APIs are insecure, but rather because so much code is still around that was built against early APIs that lacked modern security features like template-based queries. Eventually, every language gets these sorts of complaints, and always for the same reason; most code out there is in a constant state of "deprecated, but still works, so we aren't going to touch it".
This is where we disagree. The probability of a gas can's fuel-air ratio being ideal for ignition is exactly the same whether that gas can is next to another one or not. So although the probability of that specific vehicle catching fire is twenty times higher if it has twenty gas cans, the company that owns the vehicle has exactly the same chance of having a vehicle catch fire, because the probability does not decrease by adding more vehicles; it merely gets spread out over a larger number of death traps^H^H^H^H^H^H^H^H^H^H^Hvehicles.
I was assuming more like a few 5-gallon cans per vehicle—say 25 to 30 gallons in total. Two-hundred gallons would be insane. A typical half-ton pickup can't even carry that much weight; that would exceed its maximum bed weight by about 250 pounds, not counting the gasoline tanks. Besides, tanks over 25 gallons have lots of additional regulations, and most cities' fire codes won't let you store more than 25-30 gasoline cans in a single home or business, so if you go over that limit, you'd never be able to legally park the vehicle overnight....
But the tow truck has a much bigger gas tank than the pickup truck, which (assuming the tow truck isn't diesel) erases almost all of that difference.
Not really. Sugar plays a vital role in sports drinks, and moderate consumption of some alcoholic beverages has been shown to have a number of health benefits, including lower risk of heart disease.
You left out one, and it's a pretty big one. By policy, no certificate authority is allowed to issue a TLS certificate for any host in the .local domain, because there's no ownership/legitimate control over those domains, multiple people could legitimately lay claim to the same domains on different networks, and the domain names are chosen by random end users who don't even know what a TLS certificate is, much less how to buy their own domain name. Therefore, any Wi-Fi-connected device that needs to serve content via DNS service discovery must currently use an unencrypted connection.
IMO, that's a rather serious flaw in the notion of requiring HTTPS everywhere. Unlike the issues you listed, which all fall into the category of "because X hasn't upgraded Y yet" or "because X hasn't bothered to support it yet", this one is actually a problem for which there is currently no solution, and any possible solution would require completely changing the way we think about site security, moving us from a strict central trust model to something much more flexible and decentralized.
Basically, until that problem is solved, the IoT is DOA as far as HTTPS is concerned.
How is that anything more complicated than merely providing additional training data? I'm assuming that all self-driving cars will involve machine learning, no?
Tow trucks do this all the time. In some places, the police do, too. It's hard to come up with a clear reason why one truck carrying twenty properly filled, properly made gas cans is that much less safe than twenty trucks carrying one.
I would think that the existing Coast Starlight line could be upgraded for HSR, so long as you divert inland a bit to bypass downtown SLO and Santa Barbara. It would, however, be at least a 30% longer trip (or even longer if they didn't bypass those downtown areas), and that's not factoring in the extra delay caused by going slowly around that one long, tight curve (maybe where it goes around the women's prison?). The bigger problem is that they'd have to convince Union Pacific to give them priority, which is almost certainly easier said than done. And the route would also be shared with the Coast Starlight, the Pacific Surfliner, Metrolink, and Caltrain....