Mike Taylor
Mike Taylor
I believe your questions are mostly answered in https://github.com/GoogleChrome/ip-protection/issues/8 and https://github.com/GoogleChrome/ip-protection/issues/16.
Hey @blowrancebenton - really appreciate you opening this issue. Would you be able to reach out to some of the affected users and ask what versions of Chrome they're running?...
> In further testing, we found that "Disable IP Protection Proxy" on an affected computer could be enabled or disabled and the issue remained so now I'm back tracking and...
HTTP/S and DNS requests to eligible third-party domains are anonymized via the privacy proxies. We will provide additional details in an upcoming explainer on how we will determine which domains...
No, this feature will not be paid or part of a premium offering. It will be available to Chrome users as part of the core browser experience.
An HTTP/S connection will use a single pair of proxies and will present a single masked IP address to the origin. Beyond that, there are no hard constraints on different...
IP Protection will initially be available on Chrome for Android and Desktop. We continue to evaluate how to expand the protection to other platforms.
OK, I was in the wrong branch when I got those failures. So now I'm going to delete that comment for realz. The _actual_ failures are: So basically we didn't...
So I guess we need to special-case any scripts w/o `type` or `type=text/javascript` and not touch them.
@BS-Harou yeah, that's what I meant -- no type should be treated as JS.