"Blatant data gathering". I do not think you know what you're saying.
Care to prove it?
For example, here's a discussion over Google Chrome (Official, not Chromium) sends to Google (http://lifehacker.com/5763452/what-data-...out-me/all)
Basically:
- Anything you do an instant search with (that's how search suggestions work in any interface btw)
- Crash/usage statistics of the interface (can be disabled)
- Unique browser installation ids (removable via UnChrome)
- Anything that is part of a bookmarks/history/password sync (Firefox has a similar infrastructure)
Want to know where we see data leakage?
You can get it via Javascript, XSS attacks and a lot of data collection. Hell, get enough traffic logs (IP Address visited page at time) and you can learn a fuck ton.
Trust me, you're leaking more data by visiting websites than your own browser ever sends.
That's why the NSA targeted routers, data providers and datacenters. Not your personal web browser.
Also, I meant op as in op-codes (assembly).
Care to prove it?
For example, here's a discussion over Google Chrome (Official, not Chromium) sends to Google (http://lifehacker.com/5763452/what-data-...out-me/all)
Basically:
- Anything you do an instant search with (that's how search suggestions work in any interface btw)
- Crash/usage statistics of the interface (can be disabled)
- Unique browser installation ids (removable via UnChrome)
- Anything that is part of a bookmarks/history/password sync (Firefox has a similar infrastructure)
Want to know where we see data leakage?
You can get it via Javascript, XSS attacks and a lot of data collection. Hell, get enough traffic logs (IP Address visited page at time) and you can learn a fuck ton.
Trust me, you're leaking more data by visiting websites than your own browser ever sends.
That's why the NSA targeted routers, data providers and datacenters. Not your personal web browser.
Also, I meant op as in op-codes (assembly).
Slave to the Patriarchy no more