Live data from Hacker News

DuckDuckGo Challenges Google on Privacy (With a Billboard in San Francisco)

wired.com

91–100 of 224 posts

Re: DuckDuckGo Challenges Google on Privacy (With a Billboard in San Francisco)

#91
post #44

Earlier quoted context omitted.

The browser does it, and did it long before Google existed.

That doesn't mean Google couldn't or shouldn't prevent the browser from doing it. When this all started, no one envisioned ad networks and data companies aggregating all this personal information, or even that search terms would be a central part of the Internet. So now that we know what is going on, why allow this personal information to leak? As far as I can tell, the only reason is so Webmasters can do better at G…

Maybe not "when it all started" but we envisioned massive data gathering and analyzing pretty early on.

Re: DuckDuckGo Challenges Google on Privacy (With a Billboard in San Francisco)

#92
post #44

Earlier quoted context omitted.

The browser does it, and did it long before Google existed.

That doesn't mean Google couldn't or shouldn't prevent the browser from doing it. When this all started, no one envisioned ad networks and data companies aggregating all this personal information, or even that search terms would be a central part of the Internet. So now that we know what is going on, why allow this personal information to leak? As far as I can tell, the only reason is so Webmasters can do better at G…

Maybe not "when it all started" but we envisioned massive data gathering and analyzing pretty early on.

Re: DuckDuckGo Challenges Google on Privacy (With a Billboard in San Francisco)

#93
post #90

Turning off HTTP_REFERER doesn't sound like a very good idea. How would you be able to tell how people found you? Knowing what link someone came in from is a great way to see where your site fits into this world wide web of ours. It sounds to me as if the only issue is 3rd party ad networks. The antidote to this seems to me to be more reasonably the web browser's jurisdiction, ie. making the cookie policy more restri…

*referrer

Re: DuckDuckGo Challenges Google on Privacy (With a Billboard in San Francisco)

#94

Earlier quoted context omitted.

Are they passing on search terms for previous searches or just the current search? In your (frankly terrifying) example, would the site have had to have ranked for "naked bieber pics", showing up in the results and then you click it to pull the search terms? Because that would seem to be pretty innocuous.

Just the current search, but the problem is millions of pages run third-party ads, and most are run by very few networks. These ad networks can aggregate the terms and then they have previous searches as well.

Pedophilia is illegal in most countries, I'd be happy if ad networks gather data about your interest on young boys and pass it to the feds! Beasts!

Edit: judging by the downvotes, I guess a good bunch of hackers like to live in atrocity!

Re: DuckDuckGo Challenges Google on Privacy (With a Billboard in San Francisco)

#95

Earlier quoted context omitted.

That's a feature of how the internet works at an architectural level. How exactly is that Google's fault? If you don't want referral headers to be sent from one website to another, use HTTPS, or turn it off in your browser.

Unfortunately, normal people don't know how to turn them off or use the https version. Google could do a lot of things to make this easier. The best would be to just prevent ad networks from collecting this personal information altogether. The only reason I've heard against doing so is that webmasters need search terms for SEO, but they can get them via Webmaster tools. Failing that, they could make a setting in the…

> Google could do a lot of things to make this easier.

And so could Microsoft, Mozilla, Apple, and Opera.

As others have mentioned, this is a good marketing move, but it's not clear to me that you actually care that much about this issue.

Re: DuckDuckGo Challenges Google on Privacy (With a Billboard in San Francisco)

#96
post #90

Turning off HTTP_REFERER doesn't sound like a very good idea. How would you be able to tell how people found you? Knowing what link someone came in from is a great way to see where your site fits into this world wide web of ours. It sounds to me as if the only issue is 3rd party ad networks. The antidote to this seems to me to be more reasonably the web browser's jurisdiction, ie. making the cookie policy more restri…

Sorry, accidental downvote while highlighting your question.

> Turning off HTTP_REFERER doesn't sound like a very good idea. How would you be able to tell how people found you?

And what if people in general, by default, don't want you to know that and we just got it wrong by default in the browser?

Re: DuckDuckGo Challenges Google on Privacy (With a Billboard in San Francisco)

#97

Earlier quoted context omitted.

I was under the impression you can opt-out of all that, is that not the case?

No, you cannot opt-out of the referrer header. However, you can use the SSL version, which doesn't send it in most cases (still sends it for HTTPS->HTTPS traffic). Edit: sorry, I meant you cannot opt-out using http://www.google.com/privacy/ads/ or other HTTP (regular Google) settings.

You can opt out using https://encrypted.google.com/ (this has been pointed out a number of times)

Re: DuckDuckGo Challenges Google on Privacy (With a Billboard in San Francisco)

#98

This is surprisingly inexpensive advertising and will likely generate the value of its price in press coverage alone.

See that billboard directly behind it with "San Francisco Chronicle" along the top? That's for the auto show in November... 2010.

It couldn't have been very expensive if they're still advertising an event that ended two months ago...

Re: DuckDuckGo Challenges Google on Privacy (With a Billboard in San Francisco)

#99
post #44

Earlier quoted context omitted.

The browser does it, and did it long before Google existed.

Yep - if you don't want people seeing your bieberqueries, you should use SSL Google: https://encrypted.google.com/ ... or if you're super paranoid, disable sending referrer in your browser.

Firefox (at least) will still send referrer info when you navigate to a https: site from encrypted Google. You can change this in about:config by changing network.http.sendSecureXSiteReferrer to false.

Source: http://kb.mozillazine.org/Network.http.sendSecureXSiteReferr...

Re: DuckDuckGo Challenges Google on Privacy (With a Billboard in San Francisco)

#100
post #93
post #90

Turning off HTTP_REFERER doesn't sound like a very good idea. How would you be able to tell how people found you? Knowing what link someone came in from is a great way to see where your site fits into this world wide web of ours. It sounds to me as if the only issue is 3rd party ad networks. The antidote to this seems to me to be more reasonably the web browser's jurisdiction, ie. making the cookie policy more restri…

*referrer

Heh, no. The header really is "HTTP_REFERER", and is somewhat notorious for the misspelling.
Post reply on HN