5 ms·

This is actually something that browsers can mitigate. Allow users to give tracking permissions not only for subdomains, but also for paths. Deny: google.c

This is actually something that browsers can mitigate. Allow users to give tracking permissions not only for subdomains, but also for paths. Deny: google.com/* Allow: google.com/flights Something like that.

Cthulhu_ 4y ago
Yeah but, the biggest browser is Chrome, by Google; they have an incentive to allow tracking and access across their services.
- vanilla_nut 4y ago
  Indeed. If you use Chrome, you should just assume that your location is shared with Google at all times, since they likely collect it via telemetry anyway. If you use Firefox, assume your location is always shared with Mozilla via telemetry... and likely indirectly to Google as well, since they use Google Analytics for so much of their infra. Likewise for Apple/Google/Microsoft collecting data from iOS/macOS/Android/Windows. And of course your cellular provider. As far as I know the only way to ensure your personal data isn't shared with your browser publisher is to use a verifiable, open source browser that has telemetry disabled, like Iceweasel or Librewolf. And an open source, verifiable OS with telemetry disabled, like... Fedora, maybe? Manjaro? But you're being spied on by your ISP or cellular provider anyway, and the US government indirectly through your ISP and cell provider. And let's be honest, foreign governments through some combination of ISP/cellular provider/govt backdoors. Oh, and if you've read "Trusting Trust" you'll know that even OSS isn't necessarily verifiable unless you wrote the compiler yourself from scratch. So I'm not sure there's much benefit to any of it?
  - LoganDark 4y ago
    > Oh, and if you've read "Trusting Trust" you'll know that even OSS isn't necessarily verifiable unless you wrote the compiler yourself from scratch. And even a compiler you wrote yourself from scratch isn't necessarily verifiable unless you designed from scratch the hardware that you used to write it. Almost nobody knows what those Management Engines are doing!
- coffeeblack 4y ago
  Chrome users are probably okay with tracking anyway, but Firefox, Brave, Vivaldi, etc could implement more fine grained controls. Not only for geolocation.
asadotzler 4y ago
I don't think DOM permissions are going to stop Google if they want to share the data between services.

Cthulhu_ 4y ago

Yeah but, the biggest browser is Chrome, by Google; they have an incentive to allow tracking and access across their services.

vanilla_nut 4y ago
Indeed. If you use Chrome, you should just assume that your location is shared with Google at all times, since they likely collect it via telemetry anyway. If you use Firefox, assume your location is always shared with Mozilla via telemetry... and likely indirectly to Google as well, since they use Google Analytics for so much of their infra. Likewise for Apple/Google/Microsoft collecting data from iOS/macOS/Android/Windows. And of course your cellular provider. As far as I know the only way to ensure your personal data isn't shared with your browser publisher is to use a verifiable, open source browser that has telemetry disabled, like Iceweasel or Librewolf. And an open source, verifiable OS with telemetry disabled, like... Fedora, maybe? Manjaro? But you're being spied on by your ISP or cellular provider anyway, and the US government indirectly through your ISP and cell provider. And let's be honest, foreign governments through some combination of ISP/cellular provider/govt backdoors. Oh, and if you've read "Trusting Trust" you'll know that even OSS isn't necessarily verifiable unless you wrote the compiler yourself from scratch. So I'm not sure there's much benefit to any of it?
- LoganDark 4y ago
  > Oh, and if you've read "Trusting Trust" you'll know that even OSS isn't necessarily verifiable unless you wrote the compiler yourself from scratch. And even a compiler you wrote yourself from scratch isn't necessarily verifiable unless you designed from scratch the hardware that you used to write it. Almost nobody knows what those Management Engines are doing!
coffeeblack 4y ago
Chrome users are probably okay with tracking anyway, but Firefox, Brave, Vivaldi, etc could implement more fine grained controls. Not only for geolocation.

asadotzler 4y ago

I don't think DOM permissions are going to stop Google if they want to share the data between services.