4 ms·

Because Google runs ad servers. Using an ad blockers would be pointless if Google domains were allowed to bypass.

gruez 6y ago
Again, like I said previous comment google runs a bunch of other services that you can't just block the entire google ASN and not expect stuff to break. As for who's doing the blocking, there are basically two groups: enterprise sysadmins (or their vendors) and hobbyists running pi-hole at home. The former would certainly care about breakage, and likely isn't concerned about ads. Not to mention if they block safebrowsing (or google software updates) and they get hacked because of it, that'd look really bad on them. Hobbyists would care less about breakage and more about ads, but I suspect the same hobbyists don't care much for safebrowsing and probably has it disabled so whether it gets whitelisted or not is irrelevant.
- JumpCrisscross 6y ago
  > google runs a bunch of other services Trust does not compartmentalize.
  - gruez 6y ago
    The point isn't that you must trust google or anything, but that if you are serving users other than yourself, blocking the entirety of google isn't a viable option. In the case that you're only doing it for yourself, you likely have safeblocking disabled or know how to whitelist the safebrowsing endpoint yourself (it's a separate domain) that it's a non-issue.
    - JumpCrisscross 6y ago
      > if you are serving users other than yourself, blocking the entirety of google isn't a viable option This is a fair assumption to challenge. Lots of developers co-mingling their traffic with an ad company doesn't mean everyone has to whitelist their servers. It's an impediment. But Apple has navigated those.
- munk-a 6y ago
  I think that's Google's problem and very much a scenario they created for themselves. I'll give Google a lot of credit for serving the majority of their ad content off of intentionally distinct server groups but that line has been getting greyed and, if they make themselves untrustworthy, that's on them.

Again, like I said previous comment google runs a bunch of other services that you can't just block the entire google ASN and not expect stuff to break. As for who's doing the blocking, there are basically two groups: enterprise sysadmins (or their vendors) and hobbyists running pi-hole at home. The former would certainly care about breakage, and likely isn't concerned about ads. Not to mention if they block safebrowsing (or google software updates) and they get hacked because of it, that'd look really bad on them. Hobbyists would care less about breakage and more about ads, but I suspect the same hobbyists don't care much for safebrowsing and probably has it disabled so whether it gets whitelisted or not is irrelevant.

JumpCrisscross 6y ago
> google runs a bunch of other services Trust does not compartmentalize.
- gruez 6y ago
  The point isn't that you must trust google or anything, but that if you are serving users other than yourself, blocking the entirety of google isn't a viable option. In the case that you're only doing it for yourself, you likely have safeblocking disabled or know how to whitelist the safebrowsing endpoint yourself (it's a separate domain) that it's a non-issue.
  - JumpCrisscross 6y ago
    > if you are serving users other than yourself, blocking the entirety of google isn't a viable option This is a fair assumption to challenge. Lots of developers co-mingling their traffic with an ad company doesn't mean everyone has to whitelist their servers. It's an impediment. But Apple has navigated those.
munk-a 6y ago
I think that's Google's problem and very much a scenario they created for themselves. I'll give Google a lot of credit for serving the majority of their ad content off of intentionally distinct server groups but that line has been getting greyed and, if they make themselves untrustworthy, that's on them.