Nowadays, even one's typing speed between keystrokes can be tracked, serving as an additional fingerprinting datapoint (distinguish different users of same clien PC? Determine my frickin mood, or whether I'm drunk?!?)
autocomplete based on urls in history/bookmarks is fine, just ensure no remote requests occur.
(FWIW, I'm adamant about this to the extent that, if necessary, I'm happy to throw out baby with bathwater, forego autocomplete, period.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, your suggested rule perfectly addressed my immediate concern (google search autocomplete)
and I'm relieved to hear confirmation that "awesomebar" -ish autocompletion isn't planned.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nowadays, even one's typing speed between keystrokes can be tracked, serving as an additional fingerprinting datapoint (distinguish different users of same clien PC? Determine my frickin mood, or whether I'm drunk?!?)
autocomplete based on urls in history/bookmarks is fine, just ensure no remote requests occur.
(FWIW, I'm adamant about this to the extent that, if necessary, I'm happy to throw out baby with bathwater, forego autocomplete, period.)
There is no autocomplete feature in CD and won't come any.
If you are worried about google autocompletion when searching
then add the following to tracker rules:
clients1\.google\.com/complete
At least for me it stopped autocompletion at https://encrypted.google.com
Last edit: Stefan Fröberg 2014-08-03
Thanks, your suggested rule perfectly addressed my immediate concern (google search autocomplete)
and I'm relieved to hear confirmation that "awesomebar" -ish autocompletion isn't planned.