There's probably too much metal between the cargo hold and the passenger compartment for Bluetooth to work anyway. I think all actual bombs on aircraft (other than the failed shoe bomber) have been triggered by pressure switches at altitude or timers.

So it's not just that they wouldn't be stupid enough, but also that it probably wouldn't be successful even if they were.

My house is a relatively normal size (1800 square feet), and it still takes more than three full minutes for water in my shower to reach full temperature when I run it straight hot. If I also turn on both faucets in my bathroom, I can get that down to about twenty or thirty seconds, which is barely tolerable.

At my mom's house in Tennessee, the distance the water has to travel is comparable, but it takes only ten seconds or so.

It's a huge downside to all the water-saving showerheads and faucets that were forced upon us here in California decades ago. We waste a lot of time and energy to make up for a water shortage that exists only because of decades of politicians being short-sighted and kicking the desalination can down the road over and over so that the money doesn't get spent on their watch.

Translation: A company that has the potential to benefit from regulation by squeezing out competitors wants more regulation.

I'm not saying they're not right, just that it seems awfully convenient for a company specializing in pumps that recirculate data center water to want efficiency regulations that would push customers towards their most efficient (and thus presumably most high-margin) pumps.

Instead of having your hot water fan out in a tree, you wire it like a token ring with a return pipe, where each faucet only has a short bit of pipe between it and the ring. Then, you have a pump to circulate hot water through the ring-shaped pipe network. That way, it takes half a second to get hot water instead of half a minute or more.

Sure. I'd imagine most hardware vendors will want it. I'm just saying that the wording, at least as described in the summary, is... problematic at best.

I have three different browsers running, and four instances of one of them, Each has on average four windows open.

Plus there is a bunch of other stuff running, and I only have spinning rust (Being old, my brain is not very fast).

Not sure how they will get any useable info out of my PC - other than it is probably not using Windows.

Not really. It's more like requiring all vendors who sell cash registers used in restaurants to support checking photo IDs because some restaurants also serve alcohol.

There's no safe way to prove your age to a website. Any scheme requires trusting some arbitrary third party that could secretly be the government doing timing comparisons between the verification and DNS queries and stuff to unmask anonymous users. At least with operating system or browser vendors, they presumably have a strong commitment to minimizing the risk of someone publicly posting "John Doe just visited sexwithseaturtles.com" or whatever.

It's not really that terrible. If you're going to do age verification, you have two choices: browser or operating system. All else is all but guaranteed to be either a privacy disaster, a usability disaster, or both. And either way, every operating system needs to support multiple users, or the "I used dad's iPad to browse porn and buy firearms" problem makes the verification useless.

And major operating system or browser vendors that cater to the general public should make it available by default, because doing so prevents the "You downloaded the AdultCheck module, so you must be a pervert" logic that some people might use to attack people.

What's terrible is the idea of mandating that it be performed at the OS level, rather than just mandating that the OS doesn't get in the way. Browser-level verification is actually far preferable, because there's no need to bake that into an authentication framework when you can just send it out to a browser window. Leave that tiny bit of integration complexity to the companies that actually require it. But this only works if the OS supports multiple users, so that the browser's cookies and storage are not shared across multiple users.

For devices that don't have multiple users, baking it in at the OS level really is the only way, but it could just as easily be solved by baking it in at the browser level and changing the OS to allow multiple users per device. Unfortunately, such technical details are way too subtle a point for most lawmakers to understand, so obviously they did it in the most wrong way possible.

Wait 'til they realize that Android is distributed under a license that allows people to copy, redistribute, and modify it.

As usual, a law created by people who didn't think of the consequences then got modified to fix some of the worst consequences, but because they still did not think of the consequences, the modification created different consequences. And this is why we need better lawmakers.

Probably a Linux nerd (on /.? The hell you say) that carried the xST vs xDT timezone markers before the brain caught up that "Standard" and "Saving" are both "S"

> next will be Jedi training school full of pointless teen angst.

Wasn't that "The Acolyte"?

... is European startups.

Europe is Dumping Windows as fast as it can - on security grounds. Europe does not have the American funding model, and many start-ups are individuals with no significant funding.

I have developed many Xilinx projects, and failed to develop many more because I could not afford the development software. Including military applications that could have run to very high volume. At that time, there were no realistic alternatives.

Maybe, but the problem is that the electronics have to run at those temperatures and not have solder joints start popping, or other fun failures.

As far as I know, it is just real-time. And it didn't even slow down at the flashing red light. So either it recognized that someone was waving it on or it didn't see the flashing light at all.