121–130 of 396 posts
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.
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.
Firefox containers to the rescue.
This morning I looked for a similar extension for Google and I've found this fork[1] of Mozilla's extension. It's working as expected so far but I'd love for it to be officially maintained by Mozilla at some point. There is an open issue about it[2].
[0] https://github.com/mozilla/contain-facebook
Earlier quoted context omitted.
If you need OSM on Android, I can recommend: - "Organic Maps" (a fork of the old MapsMe codebase) if you want a clean, simple user experience - "OSMAnd" if you want a very powerful, highly customizable map application, which comes at the cost of a steeper learning curve Both apps are open source and support navigation, offline maps and POI search. The things I miss most compared to Google Maps is live traffic informa…
I also had some success with HERE maps: https://wego.here.com Their Android app: https://play.google.com/store/apps/details?id=com.here.app.m... Their Apple app: https://apps.apple.com/app/id955837609 The performance is good (especially on a budget Android device, better than the recent versions of Google Maps, even), they're reasonably accurate (I'm in Eastern Europe) and include navigation, traffic information, pub…
This was a life saver when roaming when data charges were really exorbitant.
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.
The threat here is google.
As other mentioned, OSM is an alternative (not equivalent) of Google Maps.
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?
You logout and switch to user B to look at another Google service, but google.com is still allowed to get your location, and will stick it to user B, which is something you might not have wanted. This didn't happen with the previous domains, so could be a surprise.
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.
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.
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?