I've got some of the Wyze v3 cameras (released in November of 2020) -- they do accept 128 GB cards.

They do have their share of limitations, but "they only take cards that are 32 gb max" isn't one of them.

That could be cool.

But it would be a lot harder to code that way, where a simple switch to turn it on and off would be quite simple.

Also, turning it on and off on a per-core basis and making sure that certain security-sensitive processes only run on the cores with it off might not work if the issues involve a cache or memory management unit or something else that may be shared between cores.

The VICP and PREP Act already protected vaccine manufacturers against liability claims and were in effect long before COVID hit, and will continue after the declared emergency is over.

That said, it's not 100% immunity and never has been, though it's fairly close -- willful conduct is not covered, for example.

True, though the article does cover both aspects of the question.

That said, what's cool about 56 microseconds/day is that that is 1/50th of a second per year -- that's significant enough that it really is something we'd have to take into account at times, but it's small enough that the vast majority of applications wouldn't care.

Ultimately, what will probably come out of this is *two* time standards -- trying to do lunar time zones doesn't make a lot of sense, so they'll probably just end up with two time scales: Lunar time and Earth time, where the former has a very slightly shorter second than the latter.

So there will probably be some "epoch" time picked where the two time scales match up, and then they will diverge, very slowly. Anything that requires extremely high precision on the lunar surface will use lunar time (and will be explicit about this), and anything that doesn't won't matter. Maybe in 50 years they could do a leap second for lunar time?

And lunar timezones won't make much sense, but working in a particular Earth timezone might make sense if they're mostly working with people on Earth in that particular time zone, and they'd probably just default to UTC otherwise.

We should do this with cars too. That would be fun!

In what seems to be more than half of the US, class 1 and class 2 e-bikes go up to 20 mph (well, the motor will help up to 20 mph -- you can go even faster, but the motor won't help), and class 3 e-bikes can go up to 28 mph. All are limited to 750 watts, which is one horsepower.

But yeah, if they're going 45 mph (without it being down a steep hill or something), that's illegal. But if there's an overall speed limit, it's 28 mph -- though it can vary from state to state.

Of course it can. Linux can run 16 bit Windows software, either in dosbox or Wine.

I did a quick test -- downloaded a 16 bit CLOCK.EXE from here, typed "wine CLOCK.EXE" ... and it just worked.

Personally, I found it strange that "string theory" got mentioned alongside Newton's laws of motion, Einstein's theories of relativity, and Schrödinger's and Dirac's equations in quantum physics -- we've actually got experimental evidence for those things.

But string theory has no direct evidence for it, and I'm not sure that we've got any solid ideas on how to obtain any.

So we're playing a game of "one of these things is not like the other ..."

Random guy off the street: "Maybe?"

Guy who's been in IT for decades: "Eh, you've always been allowed to make backups of install media, so probably not?"

BSA lawyer: "hell yes!" *cha-ching sound heard in the background*

More seriously, if the Navy only had to pay $154k for a supposed over a supposed 558k infringements of a software package that costs around $1000 for a single license, it's pretty clear that the case had to be exceedingly weak.

Well, most people aren't capable of building cells themselves.

That said, they may very well buy a bunch of loose cells and assemble them into a battery themselves (a battery = one or more cells) and they may do that themselves, but even so ... the lowest cost cells do often come from China.

Of course, if somebody builds their own battery, they may damage the cells by soldering directly to them, they may omit the protective circuitry entirely or not set it up properly or use the wrong stuff or something.

1. perhaps exactly that, and
2. don't give them ideas.

That's a whole lot easier to say than to actually do.

Either way, aviation has several ways to navigate without GPS, and they've been very reluctant to fully remove the older navigational aids because, well, GPS is great, but every once in a while it fails, and they've already got backups.

That said, inertial guidance systems tend to be expensive, larger than GPS units and can only give sufficiently accurate information for a limited time, so they're a good backup to GPS in some applications, but not all, at least not yet. Given the current situations, they probably make sense for a commercial jet airliner, maybe for a GA airplane, but probably not for the nav system in a car.

It was perhaps 15 years ago that Intel decided that consumers didn't need ECC ram, and the industry generally followed suit.

It's still common in servers, and not hard to find for workstations but for laptops? It's almost unheard of. Not totally unheard of, but almost.

DJI does track this information. And Amazon probably does keep track of serial numbers on big ticket items.

There was a case a few years ago where a helicopter and a DJI multicopters collided, and they found the owner of the multicopter based on the serial number on one of the motors that had gotten stuck in the helicopter.

Either way, DJI generally requires that you log into their apps, and from that, they'll know all the serial numbers, and possibly they'll know about all your flights and such.

Personally, I'd never suggest using DJI gear for anything criminal, they just keep too much data, and I'm not sure you can trust their disclosures about exactly what they keep and don't keep. That said, it might not be horrible if you were very, very careful about what information DJI and the place that you bought it (used might be wise) has on you, but you would have to be careful.

It's actually specific to mobile applications.

I would argue that no application on my phone should have any insight into whether I just took a screenshot or not -- that should be between my phone and me and nobody else -- but I can certainly understand why apps like twitter and snapchat take advantage of this data that the OS lets them take advantage of.

I do wish I could prevent this from happening, however.