> But DDG does not account for those privacy conscious users who may be using browsers that do allow this control. (Bias discosure: I use one and not for privac

> But DDG does not account for those privacy conscious users who may be using browsers that do allow this control. (Bias discosure: I use one and not for privacy reasons.) > The DDG decision seems to encourage users to choose browsers that have privacy-unfriendly default settings or that do not make it easy or even possible to control what if any Referer is sent. I can't follow your logic. That DDG provides their own method of circumvention for information leakage through the Referer header does not mean that it encourages browsers that don't have such features. That's like saying that a building that provides facilities for the disabled is encouraging people to become disabled. > At the very least, it tries to resolve an issue that is a clearly client-side one and is best resolved there. And you believe that that's going to happen? In a broad sense, DDG's goal is to promote privacy. The more it can help people in keeping their privacy, the better. I for one, don't control the Referer header in my browser even though I could because I'm lazy, and I appreciate DDG helping me a bit in that regard. However, I imagine that many users of DDG don't even know what a Referer header is, why complicate their search for privacy when DDG can help them? > Correct me if I am wrong but storing "settings" with DDG requires a cookie and/or Javascript to be enabled. > If this is true, then again this is not an improvement in privacy. Why? You give me the impression that you think that any use of cookies requires the ability to track a user, but that's not so. A cookie is merely data that is passed with each request. If the server receives a request "please give me search results for foo and take the following settings into account...", that's not really privacy invasive. The server is not tracking you and remembering you, you're simply providing your preferences in each request as if it were the first time that the server had ever met you. > One might wonder why DDG cannot provide an alternative search page with its form method set to POST. Users can then choose which search page they prefer. No cookie needed. It does. It's in the settings. It probably does use a cookie, but there's no privacy reason to avoid it. > Instead it sets the default method on its search pages to GET (perhaps leaking the query in the URL). > How many users will bother to change the default? A minority of them, no doubt. Like I said in the comment you replied to, the default doesn't leak to either. In the second link I shared, DDG explains how it uses a meta tag to set the URL that the browser should use for Referer. As I understand it, it doesn't even require javascript to work.