Is Chrome using the safebrowsing API endpoint in a way that's inconsistent with the docs at https://developers.google.com/safe-browsing/? Because that behaviour is entirely consistent with client side caching for distributed performance, and since it's a public API it's pretty clear that you don't have to provide any kind of identifying information to use it.
I think someone's Google foil hat is on just a little too tight. -- Charles
-- Liberationtech is public & archives are searchable on Google. Violations of list guidelines will get you moderated: https://mailman.stanford.edu/mailman/listinfo/liberationtech. Unsubscribe, change to digest, or change password by emailing moderator at [email protected].
