I’m not sure I understand Apple’s logic here. Are iCloud Photos in their data centers not scanned? Isn’t everything by default for iCloud users sent there automatically to begin with? Doesn’t the same logic around slippery slope also apply to cloud scans?
This is not to say they should scan locally, but my understanding of CSAM was that it would only be scanned on its way to the cloud anyways, so users who didn’t use iCloud would’ve never been scanned to begin with.
Their new proposed set of tools seems like a good enough compromise from the original proposal in any case.
The era you're describing is possible today if you build your own e-bike.
You can pick up a kit from ebikeling which includes standard throttles, hub motors (or mid-drive if you're into that), pedal assist sensors and displays.
You can buy one of thousands of batteries with XT60 connectors or solder one to any battery you'd like.
I recently started collecting 4K UHD Blu-Rays since I got a Samsung Q990c.
The most obvious difference to me is the audio. Though the discs do look better than say Netflix 4K, the audio is way better on my particular setup.
I do wonder if streaming is really the same "atmos" as a 4K Blu-Ray. From my experience there must be some serious compression or misrepresentation.
Will be interested in trying FlexConnect with and without Blu-Ray once it's available for me (though not sure it would be better than my current setup).
I thought the selling point of Tesla was the super fast charging? How long would it take to charge to make up the difference in reported range? Quick Google says a supercharger is up to 200 miles in 15 minutes.
They should fix the reporting though. Ideally let the user put in observed range to calibrate.
They should do the same with gas (hybrid) cars - since to be fair there’s a hit there with temperature differences and it would be neat to see the differences.
I also noticed this data is generated from aggregated user data. I wonder how a prolonged ride can affect the range. Could long rides heat the battery enough to offset the issues in cool temps?
An interesting idea, but if I’m understanding the problem trying to be solved - might be better suited by durable execution (two examples being Azure’s durable functions, and Temporal.io).
In practice transactions between arbitrary data stores would result in potentially boundless and unpredictable latency, no?
Also, is Postgres strongly consistent and linearizable)? One alternative would be using a database with stronger consistency guarantees (Spanner is but not open source, FoundationDB is but has limitations on transactions unless you implement mvcc yourself, which to be fair you are).
Perhaps just as shocking to me as this news was the fact that he was 76! Given his accomplishments and youthful demeanor in his recent communications this totally caught me off guard. That, and the fact that he lived way longer that expected, given his circumstances. Objectively a triumph. In addition to his obvious, scientific exploits, hopefully the money raised in 2014 for ALS will ensure future scientists won't have to endure such hardship.