3 ms·
Why would you need to be logged in? I'd wager that logging in simply makes the history available to you across devices. Google knows which device made the queri
by brigandish 7y ago
Why would you need to be logged in? I'd wager that logging in simply makes the history available to you across devices. Google knows which device made the queries and knows you use the device, even without any further analysis it's a good bet you made the search.
I use an application level firewall to block Chrome's outgoing connections and it took a lot of effort to get the ruleset right, even now I'm not sure it is.
Which is why I use other browsers ;-)
- cameronbrown 7y agoHow did you block outgoing connections without breaking web browsing?
- brigandish 7y agoTrial and error. I got a list of Google's IP ranges (using something like the technique in [1]) and input them into the app layer firewall and tried browsing using Chrome and nothing broke, but that's because when I use Chrome I don't browse to any Google sites. I use uMatrix on my main browser and I'm well used to breaking sites, I suppose it's increased my patience for refreshing pages until I find the magic minimum for them to work. I almost always have to turn off all kinds of blocking when doing a payment though, especially anything involving redirects, like plane tickets. Javascript is the biggest pain, IMO, next would be sites that use Recaptcha. [1] https://snurps.blogspot.com/2013/10/how-many-ip-addresses-does-google-have.html https://snurps.blogspot.com/2013/10/how-many-ip-addresses-do...