The e-Up is great, but there is still the remote control modem installed by default that lets Volkswagen « Cloud » and the app control the car remotely, and get data such as the GPS location of the car.
Except the modem doesn't work anymore because it's 3G-only and 3G networks have been switched off in a lot of places, and VW said they won't offer upgraded hardware for it.
Isn't that just what has to be selected in the play store to allow the app to access/use the localization framework in Android? It doesn't guarantee they're sharing information. They could still do it on a site by site bases with in-app approvals?
I guess the concept has gone from "We don't support this at all" to "We support it but won't be evil, you have to trust us."
How much do we trust Mozilla/Firefox? You could always go read the code yourself: https://hg.mozilla.org/mozilla-central or just do what most people do and hope someone else audits it :)
There's a choice between first party(collected) and third party(shared). Also a list of purposes one chooses from. This could include "App functionality", "Analytics", "Account management", etc...
Two of the possible 3rd party choices are "Advertising or marketing" and "Personalization". These two have been chosen for firefox. This includes sharing data with advertising partners.
A change to those options is what triggered the notification. It's not a requirement for using location features.
I'd say a part of figuring out what they are doing is reading such information. Even if the code itself doesn't reflect it yet, it's usually listed in preparation.
It's also a good way to figure out the code needs to be reviewed :)
Do you mean that it works with ha-floorplan? If so, can you please explain to me how I'd proceed to make that work because it'd be awesome.
I always wanted to do something like this but the time it takes to get the proper render and plan is just too big of an investment for me.
If you get rid of time zones, people will replace them with an ad hoc system that does most of the same things but worse. The current implementation could be improved some, but time zones in general are close to the least worst option.
I think having a unified time everywhere is a really obvious advantage. Time being measured differently based on geographic location is completely silly. You would still need to look up how a different location is scheduled but you also need to do that with timezones so there's no disadvantage, only an advantage.
It's a matter of compatibility, e.g. you're not going to start measuring length in meters when everyone else in your country is using feet. That's why I said UTC is a time zone, nobody uses it outside of the UTC time zone, therefore nobody uses it outside of the UTC time zone.
I mean each city used to have their own time zone and we got rid of that.
The next step is to just get rid of the country-sized timezones. Sure the sun doesn't rise in US West as US East at the same time but it also doesn't rise at the same time in Florida as it does in Maine.
> Hey folks. I'm the product manager for Git at GitHub. We're sorry for the breakage, we're reverting the change, and we'll communicate better about such changes in the future (including timelines).
