Yeah, that's why I almost never install any app on the Android phones I have. I default to the websites, because at least I know what the browsers leak. The apps, you never know how far they spy you. Fuck that shit.
I'm browsing through a proxy (dansguardian+squid) to filter cookies from all the sites except the ones where I want to allow them. I can run this in a VM while on the road and using W8, but at home it's in the server that acts as the gateway to the net. In fact, at home everything either uses a proxy (SOCKS or HTTP) or doesn't leave our home network. This is quite heavy and for things like Steam I need to run a script that allows the relevant ports for that one IP for a while.
A pain, but I feel it's worth it. No need to config each individual computer at home and I can trust the setup.
Google services are the worst: Whenever I use anything even remotely related to Google I instantly get "we use cookies to serve you, by using our services you approve of our cookies, blah blah blah...". Well, the moment they actually stop serving I'll just have to switch over to other providers instead then...
I really found it creepy when advertisements all over the net "changed" according to my use of Google. At the end of a holiday I would get ads that were related to my hobbies. Soon after work had started and holiday eneded my adds were flooded with IT-related things again. I clear caches and cookies often... on Unix I do it with rm, even... so that explains the "hopping" in content.
Before I set up the proxy I had not even realized that links on the Google search result pages have, at some point, stopped leading directly to target sites, but instead take a roundtrip to Google to track your click and only then forward you to the site. They weren't always like this
.
What was even more odd was that if you choose so, Google seems to use https for the search results, but it always hops back to plain http for that roundtrip? Did so at least back when I checked.
If Google ever forces to use https, I suspect they'll do it to try and stop people from filtering cookies with proxies... Why would you want to encrypt traffic between you and someone that sells information about you to make a living?
Ever since running the proxy ads have been more "random". But the proxy
does break things and
bad sometimes. Especially when it acts as the man in the middle for HTTPS (this was
not trivial to configure and takes a lot of care, because you definitely
will want some firewall rules to bypass it for some important sites). Then again, when a site does not work I often know "it's me" and I just have to open up a VM and browse directly to that site with a totally clean browser or add an exception to the proxy. Doesn't matter to me, since I use the web quite lightly relatively speaking... There are sites that are totally reliant on cookies to show anything but an error.
The thing that really sucks is that there's so little that can be done. I know I'm paranoid when I say this, but I really suspect Google, for example, is also crosscomparing source IPs and cookies automatically these days. Better to surf on a 4G stick so you can do a connection down-up regularly and are likely to get a new IP from the pool. Plus you might even be behind a NAT when using one. That should confuse them pretty nicely
h34r: .