Not if it runs the queries it sends out via a VPN where it mingles with thousands of other requests. An API call doesn’t have the disadvantages of browser fingerprinting, cookies, etc that are used to build a background of a user browsing to your search engine and track their searches. Also, there is no feedback to the search engine about which result you choose to use. If you allow outside users, it would further muddy the waters.
Ideally, you’d have it run random searches when not being used to further obfuscate the source.
Been rocking self-hosted Searxng for the last 3 weeks now as my default search engine; it’s as good or better than DDG and certainly better than Google. Results I need are usually within the first three items, no extraneous shit.
I thought I’d just try it out, but it’s staying. The ability to tune the background engines is awesome. My search history is private (though I wasn’t that worried about DDG, there was no way in fuck I was using Kagi) since it’s running it’s searches via a VPN and returning me results locally.
I’m good with a project that’s concentrating on privacy being run by a paranoid fuck. If he’s pouring all his lunacy into making it as locked down as possible, seems like a good thing to me.
I particularly like the recent duress PIN code upgrade. Seems like something every OS should have in it. I don’t need some cops fucking around with my social media and banking info because I got stopped for jaywalking.
Yah, let’s make sure to shit on the company making the only browser that even tries to preserve user privacy because the company does 1% of the shitty things Google does.
If we try hard enough, they might succumb to the constant attacks from Microsoft, Google and Apple and we’ll be left with the browser engine we deserve.
Because I don’t want a direct link to payment information and my search history stored and sold later.