131–140 of 396 posts
Genuine question. Is it reasonable as a user to expect data collected by Google via maps.google.com to not be shared with other Google applications e.g. mail.google.com? I'd have thought data collected on any of their domains would be meshed/merged behind the scenes where it suits them to do so?
Funny thing is, it depends on your threat model. Using google.com/XXX for all its services protect the user from being spied by external actors such as ISP because everything is hidden behind HTTPS. Whereas, with XXX.google.com, external actors knows that you are using service XXX.
Earlier quoted context omitted.
Also, do not fully rely on Google Maps knowing house numbers. Looks like in some areas (in UK for example) Google used some sort of OCR to find house numbers. There are houses and Wales with random house numbers that only have a house name; Numbering ends a few houses into dead-end alley where the Street View car didn't come; Or totally wrong numbers where house number sings are hard to read.
House names, rather than numbers, are very common in rural UK.
I got this a couple of years ago, and noticed immediately. Just as quickly denied the request, because I have fingers and can type my current address. It's a minor inconvenience.
How would you always know your current address? I often use maps with gps to find out where I am. Many places have no address.
Genuine question. Is it reasonable as a user to expect data collected by Google via maps.google.com to not be shared with other Google applications e.g. mail.google.com? I'd have thought data collected on any of their domains would be meshed/merged behind the scenes where it suits them to do so?
https://www.openstreetmap.org
Unfortunately this is really not an option for (some) areas in the US. After having moved to a populous LA area from Germany I was baffled at the lack of detail in the maps. Basic things like building numbers are entirely missing. Even after adding more and more details I would never fully rely on OSM here sadly. And if it only works sometimes why even bother using it in the first place? At least this was my progress…
So OSM has decent geographical coverage of the US, but relies very heavily on individual contributors to correct the deficiencies and add useful information to the maps. The only way it will be usable for you is if others have improved it. The only way it will be usable for others is if you jump back in and do the same.
This is a fantastic example of motivated reasoning. This "change" (which apparently isn't even new) can have so many different reasons, some of which are less harmful and some of which are probably worse (privacy-wise) than the one mentioned here. There is no indication that re/mis-using permissions is specifically what they wanted to do here, there is also no example of them doing it right now. Don't get me wrong, t…
Other than some abstract “branding” campaign, I cannot really see many other reasons why they would be doing this.
And as someone who worked in adtech in the past, it was very well known that Google used their domain as their tracking cookie domain as it’s nearly impossible for adblockers to just block without crippling other functionality. So they even have a history of using precisely these types of techniques.
I've tried to avoid logging into my Google account on Safari on my iPhone because I am scared of them tracking me, but I also wanted to use the Google Keep app for sharing a shopping list with my partner.
But when you launch the Google Keep app, iOS asks you whether you want to allow the app to share data with "google.com". It turns out that there is no way to sign into the Google Keep app without also signing into Google in Safari! I don't know how this works, but it is horrible! If I want to use a Google app on my phone, I basically have to give them permission to track me everywhere!
I got this a couple of years ago, and noticed immediately. Just as quickly denied the request, because I have fingers and can type my current address. It's a minor inconvenience.
Funny thing is, it depends on your threat model. Using google.com/XXX for all its services protect the user from being spied by external actors such as ISP because everything is hidden behind HTTPS. Whereas, with XXX.google.com, external actors knows that you are using service XXX.