3 ms·
I think it's the autocomplete in particular that leaks a lot of private data. I've rarely had the combined bar do a search when I didn't want it to. But I use
by wkat4242 2y ago
I think it's the autocomplete in particular that leaks a lot of private data. I've rarely had the combined bar do a search when I didn't want it to.
But I use firefox and I turned off autocomplete. And I use my own search instance (SearXNG)
- bmacho 2y agoIIRC there is no setting in Firefox to keep the content of the URL bar local.
- legacynl 2y agoHow could searchengines provide suggestions without your browser sending the url-bar content? If you want the content of your URL bar to stay local you should disable suggestions
- GoblinSlayer 2y agoThey can do it like they previously did it: provide suggestions by sending the search box content.
- legacynl 2y agoHow is that different in the case of a combined search&url bar?
- mrngm 2y agoYou'll need to explicitly navigate to the input box _designated_ for using a search engine. If I'm accidentally pasting what I thought was a URL but actually is some other text in the paste buffer in the combined input box, that text is already sent to the search engine (provided suggestions are enabled, which they are by default). If I do the same in the split URL/search box situation, and paste it in the URL box, it would at most look into the browser's history, keeping the input local.
- deleted 2y ago[deleted]
- talkin 2y ago> I think it's the autocomplete in particular that leaks a lot of private data. That’s the beauty. The whole unified input can be presented as a UX simplicity gain, while this quote points at the actual business value. ;)
- exabrial 2y agoInnovation!