janvidar
Joined 13 years ago
Joined 13 years ago
Well, it is a platform security issue - sometimes a privacy issue.
Google essentially is improving security over time by fixing broken APIs which are deprecated and removed over time.
There are plenty of security and privacy related changes where APIs have been fixed in backwards incompatible ways. Essentially, this has been solved by adding more permissions - where either Google Play, or the user needs to consent.
In order to not break backwards compatibility this has been enforced based on the "target API level", and in order to prevent malware from simply targeting old API levels, they enforce this in Google Play by forcing apps to target current API levels.
In most cases, the changes required are rather small, sometimes code changes, sometimes compliance/documentation changes - or a combination.
The standard S20 used Snapdragon in North America, and Exynos in Europe. For the S20FE the Snapdragon version was sold in Europe - which was a selling point by itself.
I did not know that the S20FE had Exynos at all until I just looked it up... Apparently version 1 does, while version 2 uses Snapdragon.
His reference ICE car is a Kia Ceed hybrid, which completed the run in 9h25m. The fastest EV: 9h35m - Yes, that was an expensive Audi. The fastest Tesla: Model S Long Range - 9h50m
All data found here: https://docs.google.com/spreadsheets/d/1V6ucyFGKWuSQzvI8lMzv...
... and the relevant videos from each test can be found on his Youtube channel: https://www.youtube.com/user/bjornnyland
Affordable EVs these days, for example the ID.3 or ID.4 do 125KW charging, at least up to a certain point. Teslas are not much better. Yes, the Model 3 can charge much faster than this, but only for a short time until it will throttle down significantly.
For this reason though, charging only a little makes even more sense. Bringing your battery from 10% to 50% should be relatively fast no matter which car you have. The last 50% will take much longer.
Once the car throttles down the charging speed, you are probably better off finding another charger an hour or two away - unless you're planning a longer stay.
At that point it becomes a nice spot to stretch your legs and grab something quick to bite before you're back on the road again.
I never charge at anything less than 75KW if I am driving long distance. I have 22KW at home for slow charging.
* A TLS client using session resumption may cause a use-after-free.
These two together provide a functional and workable environment for me. I haven't tried the DeX-station, but I believe that too could be quite workable with a phone.
The values of the regimes in control are transient and ever changing. You might be okay with it right now - but maybe not in the near future.
doubleclick.com might not be terrible for most, though.
Interesting enough, it does not add headers when accessing a country specific google domain in the EU - such as google.de or google.fr. Is that GDPR kicking in - with a nod the the brexiteers given that google.co.uk gets these headers... ?
The site says:
"Our European visitors are important to us.
This site is currently unavailable to visitors from the European Economic Area while we work to ensure your data is protected in accordance with applicable EU laws."
The legal department would care about that.
[ my public key: https://keybase.io/janvidar; my proof: https://keybase.io/janvidar/sigs/EWn9JORXe-OveLPOhZg91VfM8q3STqXavkpxXgP2VM4 ]